-
Notifications
You must be signed in to change notification settings - Fork 235
Final adjustments for finishing GitHub import #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
i'd leave issues enabled, and migrate xdist labeled issues from pytest here |
it's so strange to make a distinction for pytest-xdist plugin, why? |
Ideally this should have been the first thing to do because any problem that happens during the migration process (and believe me, they happen) will require the process to be restarted from the beginning, resulting in "stale" issues because GitHub does not allow issues to be deleted. In this case, the solution is to delete the repository and try again. Once you are satisfied on how the issues were migrated, you can continue with the rest of the migration process (code, links, etc). At least that was my experience with migrating
I think I read (I think it was in an email, but I can't find it right now) @hpk42 mentioning that it was difficult for users, when encountering a problem, to distinguish if the problem was actually a |
whats really needed is a propper multi-project bugtracker, but that seems next to impossible |
Hooray for migrating the repository to GitHub! 🎈
I think there are a few steps to finish the migration though:
The text was updated successfully, but these errors were encountered: