Moved issues should bring along as many labels as possible
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 16
- Forks
- 39
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 8
Description
When I move an issue, there are no labels set in the destination. It would be nice if the bot could bring over the labels as well, or at least as many as it can. For example, I moved an issue from manageiq to manageiq-ui-classic with the labels `ui` and `enhancement`. I would like for `enhancement` to come over, but since the `ui` label doesn't exist in ui-classic, it would be ignored.
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
No file or test is named. Start by locating the issue-move workflow and its existing tests, then trace how labels are copied between repositories. Done means destination labels that exist are preserved while unavailable labels are skipped, with tests covering both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100