move_issue needs to respect relative issue numbers
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
When you move an issue, the original issue number text gets linked afterward and doesn't correspond to the previous reference. See here: https://github.com/ManageIQ/manageiq-ui-classic/issues/1616
That is, if you reference issue #1 on the core repo, when the issue is moved it now incorrectly references issue #1 for whatever repo it moved to, which is pretty confusing.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the move_issue implementation in the miq_bot repository and trace how issue references are rewritten when an issue moves between repositories. Reproduce the example with a relative reference such as #1, then verify that the moved text still points to the original repository's issue rather than the destination repository's issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100