[llvm-dev] Accidental Remote Branches Created on Github

Mehdi AMINI via llvm-dev llvm-dev at lists.llvm.org
Fri Nov 5 20:32:02 PDT 2021


On Fri, Nov 5, 2021 at 5:56 PM Mara Sophie Grosch via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> This happening was actually a big fear for me when I got commit access,
> especially since I'm working on a fork for my hobby osdev project, not at
> all ready for upstreaming it - one wrong git push away
>
> Seeing this happening to other people is a bit of a relief
>
> Is it possible to configure GitHub to forbid that? Like everything except
> the normal branches being protected from pushes?
>

Unfortunately not: there is a "branch protection" mechanism on GitHub but
it applies only to branches after they are created as far as I know.

Pushing a random branch has little consequence, it is easy to delete:
pushing the wrong kind of things to the main branch would be more annoying
and hard-to-impossible to recover from.

Cheers,

-- 
Mehdi



>
> Mara
>
> Am 6. November 2021 00:48:49 UTC schrieb Luke Benes via llvm-dev <
> llvm-dev at lists.llvm.org>:
> >A branch containing the D112590 patch was accidentally pushed to GitHub:
> https://github.com/llvm/llvm-project/tree/efb284c07e
> >
> >In the past couple of weeks, this also happened for
> >https://reviews.llvm.org/D107347
> >and
> >https://reviews.llvm.org/D108319
> >
> >This seems to be happening a lot recently. Is there a problem with the
> instructions to commit patches?
> >
> >_______________________________________________
> >LLVM Developers mailing list
> >llvm-dev at lists.llvm.org
> >https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20211105/573af6cb/attachment.html>


More information about the llvm-dev mailing list