On Thu, Nov 12, 2020 at 12:07 PM Oleg Nenashev <[email protected]> wrote:
> Since this is a request for a new repo creation (not a fork/move) && there > is a consensus here, I do not see a particular need. A HOSTING ticket would > be useful to understand the desired permissions, but we can figure it out > as we go. > So are you saying that anyone can circumvent hosting processes by asking for a new repo "to push existing code"? Because that's what I'm hearing. (FWIW we stopped doing this several years ago because we customize repos in the ircbot code, set up permissions – which you've already noticed is a problem now – and apply some other custom defaults. Plus having empty repos around that never got populated for months or years is also not great.) -- 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/CAMo7Pt%2BtmogApuyJkNET8gmV0sr8%2Bs3og3x8NSw%3DJrV3o7CAPg%40mail.gmail.com.
