Ah, I thought the "forking process" was the default behaviour when adding a plugin to the JenkinsCI organisation. Thank you all for your answers, indeed breaking the fork link is the simpler solution. I'll ask github directly.
Kind regards Aurélien On Fri, Aug 26, 2022 at 6:42 PM Basil Crow <m...@basilcrow.com> wrote: > On Fri, Aug 26, 2022 at 9:36 AM 'Gavin Mogan' via Jenkins Developers > <jenkinsci-dev@googlegroups.com> wrote: > > > > Advantage of jenkins being the source is that github search will work > org wide for it. > > Also, CD is only supported when the GitHub repository is in the > jenkinsci GitHub organization. In general I think we prefer for all > plugins hosted on our Update Center to have their repository of record > in the jenkinsci GitHub organization, although there are a few > exceptions for historical reasons. That enables us to manage > repository write access and Artifactory upload permissions using our > unified and well-documented system. > > -- > 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 on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAFwNDjrn0AVSLR6HGAchUi8R8ixa%2BkygmV3uctbeA_UY0Dd7QQ%40mail.gmail.com > . > -- 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 on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAP4BqYmp8aY2FVHdcfeLxawZ7irjtYLO3j6Gv429yDjqYq7q_w%40mail.gmail.com.
