-
Notifications
You must be signed in to change notification settings - Fork 18
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
keep github ids in sync with trac ids even if trac has no consecutive ticket ids #28
Comments
bwl21
pushed a commit
to bwl21/trac-hub
that referenced
this issue
Mar 12, 2019
…s id are not consecutive
Looking forward to your PRs. I can see you've already spent quite some time enhancing the tool. Thanks in advance! |
bwl21
pushed a commit
to bwl21/trac-hub
that referenced
this issue
Mar 22, 2019
ronaldtse
added a commit
to riboseinc/trac-hub
that referenced
this issue
Jul 4, 2021
* bwl21-master: updated readme with hint to gitlab This is the wrap-up of my migration done based on tram-hub optimized ticket opening now handle attachments .gitignore .idea improve layout of transferred tickets - separate labels from badges export trac states to info improve logging and feedback to the user improve mapping of changes references improve mapping of assignee fixed milestone due dates replace full ticket urls by appropriate ticket links fix handling of revmap now handle milestones, some refinement of ticket layout see mavam#26 created a docker file to run trachub mavam#27 adapted markdownify to process header 1 correctly and not place ticket content in a quote see mavam#28 keep github and trac numbers in sync even if trac tickets id are not consecutive see mavam#30 implemented info in ruby
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Request
By whatever reason we have deleted a bunch of tickets in our trac. I now would like to migrate trac into a fresh github project. Is there a way to ensure that the id in github are the same as in trac, even if the ids are not consecutive.
This is the opposite case than the one when we do in an exisitng github repository which already has issues.
Solution approach
The text was updated successfully, but these errors were encountered: