Hi Brad, Am Sonntag, dem 28.12.2025 um 18:16 -0700 schrieb Brad Walker: > [Trivial change (remove unnessary cast) > Given that resources are constrained, I wonder if it's "necessary" for me > to submit a code review if all I'm doing is removing the redundant cast. > Rather just merge it?
there are two different possible interpretations of this: 1. create a PR, wait for tests and if green merge without review 2. merge to master directly without running tests and creating a PR I think Michael already gave a good answer, my interpretation of our current operations is: (1) is ok and in fact I already did this multiple times. There are areas in the NB codebase, that are not to widely known or of interest to others, then there is no benefit in not getting fixes in. I think that the given example could be fast tracked like this. (2) is _not_ ok for general changes. Even the changes while running releases, which don't change code, are run through the pipelines. The big benefit is, that the test cascade costs little, but can prevent huge headaches. At times it is frustrating to be required to restart failing checks, but I think it is worth it. Greetings Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
