On 2 February 2016 at 20:32, Daniel Beck <m...@beckweb.net> wrote: > > The problem we sometimes have is that someone creates/asks for creation of > a repo, and then does nothing to add content.
I get the objective. > The safer approach therefore is to fork another repo. Since forking an > effectively empty repo would be pointless and have the same problem, > forking should only be done once actual content has been pushed to that > repo. > I don't get this part. I ultimately want to end up with a "jenkinsci/pipeline-rest-api-plugin" repo. What are you suggesting I fork to get to there? Are you suggesti ng that I create a repo in my own account and fork it into jenkinsci? -- 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/CA%2BbPao%2BBQabB321f53%2BDsHD8SYiS4LN1u9dusJxa%2B6r%2BGvPGqQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
