Hey everyone, I noticed that some committers occasionally create dev branches under the main apache/calcite repository [1].
Working directly under the main apache/calcite repo has some side effects: * Extra noise and duplicate notifications in commits list [2] * Duplicate CI runs on Jenkins [3] and GitHub [4] * Maintenance overhead to get rid off the branches once development cedes I am not against this contribution model although the fork-based contribution workflow is more commonly used and does not have the above side-effects. If there is no particular reason for creating branches under the main repo, I would favor the fork-based approach. Best, Stamatis [1] https://github.com/apache/calcite/branches/all [2] https://lists.apache.org/[email protected] [3] https://ci-builds.apache.org/job/Calcite/job/Calcite-sonar/ [4] https://github.com/apache/calcite/actions?query=
