Skip to content
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

Retire old identifiers and point to new identifiers #159

Closed
1 task
kayceesrk opened this issue Feb 20, 2024 · 0 comments · Fixed by #218
Closed
1 task

Retire old identifiers and point to new identifiers #159

kayceesrk opened this issue Feb 20, 2024 · 0 comments · Fixed by #218
Labels
enhancement New feature or request
Milestone

Comments

@kayceesrk
Copy link
Contributor

kayceesrk commented Feb 20, 2024

Consider the work items for the teams: https://github.com/orgs/tarides/projects/25/views/1. Some legacy work items have two ids -- a legacy id which is AAAnnn and the new id, which is the issue number. For example, "Merlin supports occurrences" has a legacy id Mer7 and a new id, which is tarides/workitems#2. It is better to retire the old id and use the new one for many reasons

  1. The uniqueness of old identifiers comes from old processes (needed to be generated by Gemma and Wafae), which we no longer follow. The string names are not unique by themselves, whereas the new ids are guaranteed to be unique.
  2. We don't have legacy ids for many new WIs
  3. Github knows about new ids. For example, the plaintext tarides/workitems#2 is rendered as a URL. See tarides/workitems#2.

Tasks

@gpetiot gpetiot added the enhancement New feature or request label Feb 20, 2024
@gpetiot gpetiot changed the title Retrire old identifiers and point to new identifiers Retire old identifiers and point to new identifiers May 7, 2024
@gpetiot gpetiot added this to the 1.0.0 milestone May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants