So that's usually branch protection settings in GitHub. I've personally never found a way to support mvn release and have branch protection enabled.
You could disable the no pushes while you do the release. I bet there's also a way to tell mvn to use a branch On Fri., Jan. 21, 2022, 7:45 a.m. Alberto Bec, <[email protected]> wrote: > Forgot to include screenshot > > On Friday, January 21, 2022 at 10:43:59 AM UTC-5 Alberto Bec wrote: > >> I'm trying to publish our plugin using the manual method >> <https://www.jenkins.io/doc/developer/publishing/releasing-manually/> but >> getting the error "remote: error: GH006: Protected branch update failed for >> refs/heads/master." >> >> Do I need to do this in a branch then merge that into master? Or am I >> missing a permission? >> > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/bae55f98-1324-44f5-9d94-a3bbe034220cn%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutMr4R1rthU0bXWMrjy9dmmQrrkf9AfXfP1qDKKZqS6OA%40mail.gmail.com.
