On Tuesday, September 27, 2022 at 3:29:10 AM UTC-7 tobias...@gmail.com wrote:
> One more question: The current plan is to use the sagetrac-mirror repo as > the base for creating PRs but also to archived it. However, if I'm not > mistaken, that makes all branches in sagetrac-mirror readonly and thus one > cannot continue working on existing PRs by pushing to the corresponding > branch in sagetrac-mirror. Thanks for catching this. I have revised https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b#conversion-of-trac-tickets-and-the-trac-wiki-to-github as follows: 1. Make a fork of sagemath/sagetrac-mirror called sagemath/sagetrac-archive and archive <https://docs.github.com/en/repositories/archiving-a-github-repository> it (= set it to readonly). 2. Open PRs from sagemath/sagetrac-mirror <https://github.com/sagemath/sagetrac-mirror> to the new repo for all open tickets with attached branches. -- 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/be783180-49ff-4bf3-8d2d-f8db3bad749bn%40googlegroups.com.
