On Fri, Sep 30, 2022 at 8:59 AM Marc Mezzarobba <m...@mezzarobba.net> wrote: > > John H Palmieri wrote: > > You would think that this would be a solved problem: others in the > > open source community must have be in the practice of backing up their > > GitHub info. > > The following tools seem fairly complete: > > - https://github-backup.branchable.com/ (but I'm getting timeouts with > it), > > - https://github.com/josegonzalez/python-github-backup (not tested). > > IMO we should at the very least have something like that running before > making the switch. We should also refrain from using features of github > not supported by our backup tool.
While migrating to github, we can get json records for each issue we created to replace tickets. (they are complete records, everything may be recreated from them) Then we can set up a GitHub actions to produce such jsons for created/updated issues and PRs, see e.g. https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#issue_comment I think this is more robust than running tools which make global copies. (These updated jsons need to be be stored somewhere) Dima > > -- > Marc > > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/th67k9%246eq%241%40ciao.gmane.io. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq1qC8%3DnOmW84TgPR6AvNMu-EN8DXAXkBSk8t%3DzOegVLZA%40mail.gmail.com.
