Hi, > - How to delete pascal-brand38, a former developer who has left the company, and does not appear in the YML declaration file?
>From github configuration? If you are admin on the repository, you should be able to do so https://github.com/jenkinsci/mathworks-polyspace-plugin/settings/access. > - How to submit https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-mathworks-polyspace.yml (I am getting an error 403)? You need to fork the repository, create a branch (recommended) and commit you changes within that branch. Then push the branch to your fork (new remote). Finally, you'll be able to submit a pull request from GitHub web interface using your branch as the source and the `master` branch of the jenkins-infra/repository-permissions-updater repository as the target. Le lun. 5 mai 2025 à 09:58, Stéphane BOBIN <stephane.bobin...@gmail.com> a écrit : > Hi Daniel! > > Thanks for clarifying about Kevin. > > Any idea about: > > - How to delete pascal-brand38, a former developer who has left the > company, and does not appear in the YML declaration file? > - How to submit > https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-mathworks-polyspace.yml > (I > am getting an error 403)? > > Thanks! > > -- Stéphane > > Le mar. 22 avr. 2025 à 15:15, 'Daniel Beck' via Jenkins Developers < > jenkinsci-dev@googlegroups.com> a écrit : > >> >> On Thu, Apr 17, 2025 at 4:40 PM Stéphane BOBIN < >> stephane.bobin...@gmail.com> wrote: >> >>> >>> - Kevin-CB: I don't even know this guy, how could he ever get >>> permissions??? >>> >>> Kevin-CB is a member of the Jenkins security team and he has Maintain >> permission in all repos of the jenkinsci org to be able to prepare and >> publish security updates without needing assistance of an org owner. This >> is our first use of org-level permissions and only temporary until we've >> improved our automation, so this account is not hidden from this list >> (unlike what we do with org owners, of which there are several, including >> other security team members). >> >> -- >> 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 jenkinsci-dev+unsubscr...@googlegroups.com. >> To view this discussion visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BOvgSzMgEBu%3Dw9hNBaS04KFBnLmoZsiV4m8JemmR_ZEw%40mail.gmail.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAMo7Pt%2BOvgSzMgEBu%3Dw9hNBaS04KFBnLmoZsiV4m8JemmR_ZEw%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAMQQ2sk8cioqVnqsdCA25MjiZe9AHO8FstupcW1UU6i4V78pAA%40mail.gmail.com > <https://groups.google.com/d/msgid/jenkinsci-dev/CAMQQ2sk8cioqVnqsdCA25MjiZe9AHO8FstupcW1UU6i4V78pAA%40mail.gmail.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 jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKwJSvxCFdG6LWP9y6cLxwaD6v_dqeZYHW3mcrZFkWS0cD4-cA%40mail.gmail.com.
