> Which would be a downside I think. Oh I thought that was the intention
Yea for sure a downside On Wed, Aug 28, 2019 at 11:56 AM Jesse Glick <jgl...@cloudbees.com> wrote: > On Wed, Aug 28, 2019 at 12:31 PM 'Gavin Mogan' via Jenkins Developers > <jenkinsci-dev@googlegroups.com> wrote: > > That would break the fork linkage > > Which would be a downside I think. Also the current method forces you > to remember to delete your own account’s clone so the @jenkinsci one > does not appear as a fork of it. > > Also you would lose any existing issues, PRs, etc. > > The repository transfer operation seems like the most intuitive and > least problematic approach. > > -- > 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/CANfRfr1_d16DVnis%3DQRpZa5R%3D_VXaw94pr%2BCLyHL%2BuBz%3DF64bw%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/CAG%3D_DutDuG5o9bBrGwCX3-JvOkqzocb%3DqEFk8c%2BVwqN4kxvLVQ%40mail.gmail.com.
