+1 on Tim's proposal. On Wednesday, 17 August 2022 at 07:48:25 UTC+2 [email protected] wrote:
> So it's just all the old repos at once they have issues with? They are > still okay with one off requests to fix a repo? > > I wonder if they have a private API we could use that would prevent us > from having to download then upload to prevent the fork > > On Tue, Aug 16, 2022, 10:42 p.m. Tim Jacomb <[email protected]> wrote: > >> It currently still forks although there’s instructions telling people to >> delete their repo or raise a support ticket if it gets messed up >> >> On Wed, 17 Aug 2022 at 00:29, 'Gavin Mogan' via Jenkins Developers < >> [email protected]> wrote: >> >>> This is a one time operation for all past repos? What happens to all the >>> new ones? Is the script pushing a new repo now (I forgot)? >>> >>> Totally on board with fixing all the old repos, not being able to search >>> them kinds sucks. >>> >>> On Tue, Aug 16, 2022 at 4:05 PM Mark Waite <[email protected]> wrote: >>> >>>> +1 from me >>>> >>>> On Tue, Aug 16, 2022, 2:32 PM Tim Jacomb <[email protected]> wrote: >>>> >>>>> GitHub support have offered to make the jenkinsci organisation the >>>>> root of all of the fork networks >>>>> >>>>> See >>>>> >>>>> https://github.com/jenkins-infra/helpdesk/issues/2272#issuecomment-1216867119 >>>>> >>>>> >>>>> Any objections or +1s? >>>>> >>>>> Thanks >>>>> Tim >>>>> >>>>> On Wed, 4 Aug 2021 at 16:52, Tim Jacomb <[email protected]> wrote: >>>>> >>>>>> I replied with Daniel's support ticket number (569994) >>>>>> >>>>>> and got this back: >>>>>> >>>>>> Hi Tim, >>>>>> >>>>>> Thanks for your patience here. I checked internally once more and >>>>>> found that we can, in fact, do this for you. We've gone ahead and >>>>>> detached >>>>>> the repository into its own fork network. >>>>>> >>>>>> Feel free to reach out if you have any additional questions about >>>>>> this! >>>>>> >>>>>> On Wed, 28 Jul 2021 at 17:38, Slide <[email protected]> wrote: >>>>>> >>>>>>> It would be super ideal to do transferring if we could figure out a >>>>>>> good process for it, we lose GitHub Issues and some other things when >>>>>>> we >>>>>>> fork as is. >>>>>>> >>>>>>> On Wed, Jul 28, 2021 at 8:33 AM Tim Jacomb <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Wouldn't creating a repo and pushing the code instead of forking >>>>>>>> work during the hosting process? >>>>>>>> >>>>>>>> >>>>>>>> On Wed, 28 Jul 2021 at 15:02, Jesse Glick <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> On Wed, Jul 28, 2021 at 2:48 AM [email protected] < >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> Seem's like GitHub won't break the fork relationship anymore >>>>>>>>>> without both sides agreeing to it? >>>>>>>>>> >>>>>>>>> >>>>>>>>> This could be a real problem for us. We still have a bunch of >>>>>>>>> repos with misleading fork status, like >>>>>>>>> https://github.com/jenkinsci/plugin-pom rather prominently. There >>>>>>>>> should be some provision by which a “fork” which has way more >>>>>>>>> activity than >>>>>>>>> the “origin” can unilaterally break the relationship. Of course you >>>>>>>>> can >>>>>>>>> delete and recreate the repo with Git history intact but you will >>>>>>>>> lose all >>>>>>>>> PR history, which is intolerable. >>>>>>>>> >>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to a topic in >>>>>>>>> the Google Groups "Jenkins Developers" group. >>>>>>>>> To unsubscribe from this topic, visit >>>>>>>>> https://groups.google.com/d/topic/jenkinsci-dev/SkKoCccPrOc/unsubscribe >>>>>>>>> . >>>>>>>>> To unsubscribe from this group and all its topics, send an email >>>>>>>>> to [email protected]. >>>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%40mail.gmail.com >>>>>>>>> >>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr1XZbUvJER_5-LMFd8i1d1RTaFy6JPLhwq9pG9uLE_ZVg%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 [email protected]. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie4r6MsTyNum4R57DSe3eMO7yNSVt1qbndVZviE%3D57Eug%40mail.gmail.com >>>>>>>> >>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bie4r6MsTyNum4R57DSe3eMO7yNSVt1qbndVZviE%3D57Eug%40mail.gmail.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Website: http://earl-of-code.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 [email protected]. >>>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5HMgWmy%2BrQbnTH1p02Ngo9dXfqtR19SG%3DcxR_NLyWxw%40mail.gmail.com >>>>>>> >>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAPiUgVf5HMgWmy%2BrQbnTH1p02Ngo9dXfqtR19SG%3DcxR_NLyWxw%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 [email protected]. >>>>> To view this discussion on the web visit >>>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bid6aSGqdh_JCMjvmANiin4TVbvOnMRLKGbF%2B89uM5iDFg%40mail.gmail.com >>>>> >>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bid6aSGqdh_JCMjvmANiin4TVbvOnMRLKGbF%2B89uM5iDFg%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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHBOeuV4ZFPJXsRSfbiKZebUExEdyuyU%2B0EKjTr09nZWw%40mail.gmail.com >>>> >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHBOeuV4ZFPJXsRSfbiKZebUExEdyuyU%2B0EKjTr09nZWw%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 [email protected]. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuRwO2B1eV4RiQb_%2B1oyzjuZdoxmzq%3DLTw_R-D6Tpq5zw%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuuRwO2B1eV4RiQb_%2B1oyzjuZdoxmzq%3DLTw_R-D6Tpq5zw%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 [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidzg-4X3X_J%3DYiPiZLZzLWZ%2BvrgTSWY%2B2FneEyKYOuUoQ%40mail.gmail.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3Bidzg-4X3X_J%3DYiPiZLZzLWZ%2BvrgTSWY%2B2FneEyKYOuUoQ%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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/c702e3fd-764d-4470-b9a8-ba6c87a3d3a8n%40googlegroups.com.
