Actually I see I now have write access. Thanks! I think we would also need admin access, or for somebody with admin access to rest the hooks settings on the repository.
AFAIR jenkinsci organization defines default hooks for http://ci.jenkins.io/ but it seems this repository is overriding them. Details in https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/28 On Monday, January 21, 2019 at 2:29:34 PM UTC+1, Jakub Bocheński wrote: > > PPS. Just in case: I am talking about access to > https://github.com/jenkinsci/stash-pullrequest-builder-plugin not the one > at nemccarthy/stash-pullrequest-builder-plugin > > On Monday, January 21, 2019 at 1:32:13 PM UTC+1, Jakub Bocheński wrote: >> >> PS. I mean probably something is wrong wrt those settings for >> stash-pullrequest-builder-plugin repository, but having no access I can't >> check: >> >> >> [image: Screenshot_20190121_132945.png] >> >> >> On Monday, January 21, 2019 at 1:27:16 PM UTC+1, Jakub Bocheński wrote: >>> >>> > Invited you again. >>> >>> I still have only read access (not the invite text says "gives *pull* >>> access to 1 jenkinsci repository."). >>> I'm guessing maybe there is some setting on the repository level for >>> that only gives read access to members? Unfortunately I can't check that. >>> This is what I see at >>> https://github.com/orgs/jenkinsci/teams/stash-pullrequest-builder-plugin-developers/repositories >>> [image: Screenshot_20190121_132018.png] >>> >>> >>> >>> >>> This is what I see for logstash-plugin >>> https://github.com/orgs/jenkinsci/teams/logstash-plugin-developers/repositories >>> >>> , which I'm also maintaining: >>> [image: Screenshot_20190121_132242.png] >>> >>> >>> >>> >>> > Note that this file is only about deployment permission for releases, >>> and is fully unrelated to GitHub merge permission. >>> >>> Right, sorry I got the two confused. >>> >>> On Monday, January 21, 2019 at 1:02:21 PM UTC+1, Baptiste Mathus wrote: >>>> >>>> You have to file a PR there yourself if you want access. >>>> Note that this file is only about deployment permission for releases, >>>> and is fully unrelated to GitHub merge permission. >>>> >>>> Invited you again. >>>> >>>> [13:01] <+ batmat> | jenkins-admin: make jakub-bochenski committer >>>> on stash-pullrequest-builder-plugin >>>> [13:01] <@jenkins-adm> | Added jakub-bochenski as a GitHub committer >>>> for repository stash-pullrequest-builder-plugin >>>> >>>> >>>> Le lun. 21 janv. 2019 à 11:35, Jakub Bocheński <[email protected]> >>>> a écrit : >>>> >>>>> Bump? >>>>> I see only "nemcarthy" here, neither me nor @jimklimov >>>>> <https://github.com/jimklimov> is listed in >>>>> https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-stash-pullrequest-builder.yml >>>>> >>>>> On Friday, January 18, 2019 at 4:32:51 PM UTC+1, Jakub Bocheński wrote: >>>>>> >>>>>> Hey, I couldn't find any invites, all I got is this email >>>>>> >>>>>> You’ve been added to the stash-pullrequest-builder-plug >>>>>>> in Developers team for the Jenkins organization. >>>>>>> stash-pullrequest-builder-plugin Developers has 2 members and gives >>>>>>> *pull* >>>>>>> access to 1 jenkinsci repository. >>>>>>> >>>>>>> View stash-pullrequest-builder-plugin Developers: https://github >>>>>>> .com/orgs/jenkinsci/teams/stash-pullrequest-builder-plugin-developers >>>>>>> >>>>>>> Read more about team permissions here: https://help.github >>>>>>> .com/articles/what-are-the-different-access-permissions >>>>>>> >>>>>> >>>>>> I still don't have write permissions. >>>>>> >>>>>> *@Baptiste Mathus* can you help please? >>>>>> >>>>>> On Friday, January 11, 2019 at 5:37:10 PM UTC+1, Baptiste Mathus >>>>>> wrote: >>>>>>> >>>>>>> Done. Thanks a lot for the involvement and the patience @Jakub! >>>>>>> You should have received an invitation that you *must* accept to get >>>>>>> merge/push access. >>>>>>> >>>>>>> FTR >>>>>>> [17:33] <+ batmat> | jenkins-admin: hello ! >>>>>>> [17:33] <@jenkins-adm> | Hello batmat! >>>>>>> [17:34] <+ batmat> | jenkins-admin: make jakub-bochenski >>>>>>> committer on stash-pullrequest-builder-plugin >>>>>>> [17:34] <@jenkins-adm> | Added jakub-bochenski as a GitHub committer >>>>>>> for repository stash-pullrequest-builder-plugin >>>>>>> [17:34] <+ batmat> | jenkins-admin: make jbochenski the lead of >>>>>>> stash-pullrequest-builder-plugin >>>>>>> [17:34] <@jenkins-adm> | Changing default assignee of subcomponent >>>>>>> stash-pullrequest-builder-plugin to jbochenski >>>>>>> [17:34] <@jenkins-adm> | Default assignee set to jbochenski >>>>>>> >>>>>>> Le ven. 11 janv. 2019 à 17:33, Baptiste Mathus <[email protected]> a >>>>>>> écrit : >>>>>>> >>>>>>>> Given the level of activity of the plugin (last (failed AFAICT) >>>>>>>> release 2 years ago), I'm going to move forward here even if the >>>>>>>> timeout of >>>>>>>> two weeks is not fully reached yet. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Le jeu. 3 janv. 2019 à 16:41, Jakub Bocheński <[email protected]> >>>>>>>> a écrit : >>>>>>>> >>>>>>>>> Hi, >>>>>>>>> I'd like to become a maintainer of >>>>>>>>> https://plugins.jenkins.io/stash-pullrequest-builder >>>>>>>>> >>>>>>>>> The plugin is not listed as "for adoption" but it looks abandoned. >>>>>>>>> There has been no response since October here >>>>>>>>> https://github.com/nemccarthy/stash-pullrequest-builder-plugin/issues/150 >>>>>>>>> I've also created a JIRA ticket in December, also no reply: >>>>>>>>> https://issues.jenkins-ci.org/browse/JENKINS-55148 >>>>>>>>> Github doesn't show any author's activity in the project for far >>>>>>>>> more than that (~ since Jan 2017). >>>>>>>>> >>>>>>>>> I don't have big plans for the plugin just want to merge some >>>>>>>>> obvious bug fixes: >>>>>>>>> >>>>>>>>> https://github.com/nemccarthy/stash-pullrequest-builder-plugin/pull/149 >>>>>>>>> https://issues.jenkins-ci.org/browse/JENKINS-41771 >>>>>>>>> https://issues.jenkins-ci.org/browse/JENKINS-51480 >>>>>>>>> https://issues.jenkins-ci.org/browse/JENKINS-55153 >>>>>>>>> >>>>>>>>> CCing the git commit email of previous maintainer. >>>>>>>>> >>>>>>>>> Best regards, >>>>>>>>> Jakub Bocheński >>>>>>>>> >>>>>>>>> -- >>>>>>>>> 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/CAGiELgqCrojXADpQEgrRn%3DotqQfT7T5gUC43a02o9YB_GTMY_g%40mail.gmail.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAGiELgqCrojXADpQEgrRn%3DotqQfT7T5gUC43a02o9YB_GTMY_g%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>>> >>>>>>>> -- >>>>> 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/1f4c2ef0-9cf3-43d4-93d9-0474c5a4924e%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/1f4c2ef0-9cf3-43d4-93d9-0474c5a4924e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> -- 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/824142a5-0f1e-4169-8ee3-a9b62e2834c0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
