I think we could ask Infra to set some 'protected' branches, which means we can not do force push on these branches, but I'm not sure if it is possible to forbid a simple push...
In my experience, I've pushed wrong commits to the repo when developing projects in ASF, and usually the solution is to add another commit to rever the wrong commit... Gregory Nutt <spudan...@gmail.com> 于2020年4月28日周二 上午10:44写道： > > > No sure what happen, maybe I push the wrong remote git? Does github > > have any configuration to enforce all merge must come from web UI? > > In this case, AFAIK no harm was done. A little bit a odd history was > added but no file changes. So I think we are good. We do need to be > careful; all of us will do this sometime so we do need some mechanism to > monitor direct changes. I am sure I will be on the wrong branch or > wrong clone sometime too. > > I don't think we can just forbid direct changes because we do need to do > some direct changes, for example, to rebase branches. Perhaps there is a > web UI for that too, but I have been doing that manually. > > It would be nice to be able to filter email on comm...@nuttx.apache.org > to detect unusual behavior. If we can't prevent the modifications, it > would at least be nice to get sparse notifications of any unusual > activity. Right now, we depend on someone with sharp eyes catching such > things (thanks to Abdelatif to has the best eyes I know of). > >
