It's up to the community to decide if they want to allow force pushes or not. Personally, I am OK with allowing force pushing to main assuming that it is not abused and is preceded with a heads-up to the mailing list.
A use-case where someone force pushes immediately after realising a problem with the original commit is usually fine and not really disturbing. Moreover, all the git hashes are archived to the mailing lists so even if someone messes up badly with force-pushing things can be rectified. Best, Stamatis On Fri, Mar 8, 2024 at 10:36 PM Ashvin A <ash...@apache.org> wrote: > > Hello All, > > Please note that quash and merge has been disabled in the GitHub UI > (PR-372), to ensure that the committer's name is correctly represented in > the commit message. > > Consequently, it is important that PR authors squash all commits before the > PR is approved and merged into main. Failing to do so can result in noisy > and confusing updates on the trunk. Recently, I misunderstood this and > ended up creating 17 commits on the trunk originating in PR-352 that fixies > the project name in the docs and website pages. > > Commits on main cannot be reverted, main branch is protected and force push > is disabled on github and on gitbox. > > All committers and reviewers must enforce this requirement. Let's discuss > this further on Monday (first community sync meeting at 8AM PST, March 11 > 2024). > > Best, > Ashvin
