> I'm guessing that for this particular instance, someone could fork the repo > and then open a PR from their SocketCAN branch to our master? But.....
We can open a pull request from the main repo. What Xiang is suggesting is to only protect master or any other branch pattern we want. That won't affect all branches in the repo. But again, Github only prevents force pushing. Maybe what we need is to add something locally by a pre-push hook. On Tue, Apr 28, 2020 at 3:49 PM Nathan Hartman <hartman.nat...@gmail.com> wrote: > > On Tue, Apr 28, 2020 at 10:38 AM Gregory Nutt <spudan...@gmail.com> wrote: > > > > The maintainer still can create a new branch and push to that branch > > directly, only the master branch get the strict protection. The setting > > must be done by INFRA team, I can raise a JIRA ticket if the community > > agree that it's the right direction to go. > > > > How would we perform development on a feature branch. We have one now, > > the SocketCAN branch, which is complete and ready for review into master > > (AFTER we straighten out some SGA/CCLS issus). Would we be able to > > merged the feature branch onto master? > > > I'm guessing that for this particular instance, someone could fork the repo > and then open a PR from their SocketCAN branch to our master? But..... > > This might be a good idea, but we also need to make sure that it is > > consistent with out still-incomplete-after 5 months workflow document. > > How do we do shared development on a feature branch? > > > Yes, that would screw up shared development on a feature branch... :-( > > Nathan
