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

chore: replace status: label from issue with status:in-progress once targeted with PR #8965

Closed
HonkingGoose opened this issue Mar 3, 2021 · 3 comments
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality) won't do

Comments

@HonkingGoose
Copy link
Collaborator

What would you like Renovate to be able to do?

Issues get labeled status:requirements and status:ready on a consistent basis, which is good.
We are nowhere near as consistent with applying the status:in-progress label for things that are in progress.

I see issues targeted with a PR still say: status:requirements or status:ready, while they should be status:in-progress.. 😄

Did you already have any implementation ideas?

Find a way to automate replacing the status:ready and status:requirements labels with status:in-progress when a PR targets the issue for closure. If the issue gets targeted with a PR, that's a definite sign that somebody is working on implementation.

@HonkingGoose HonkingGoose added priority-5-triage status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) priority-4-low Low priority, unlikely to be done unless it becomes important to more people and removed priority-5-triage labels Mar 3, 2021
@rarkins
Copy link
Collaborator

rarkins commented Mar 3, 2021

On PR open or PR body update we should:

FYI I checked GitHub's GraphQL scheme for PullRequest and it doesn't appear to have any way to query a PR to find the list of associated issues it resolves, so therefore I suggest doing the query ourselves

@rarkins rarkins added status:ready and removed status:requirements Full requirements are not yet known, so implementation should not be started labels Mar 3, 2021
@HonkingGoose

This comment has been minimized.

@rarkins

This comment has been minimized.

@rarkins rarkins closed this as completed Jan 13, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 13, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:feature Feature (new functionality) won't do
Projects
None yet
Development

No branches or pull requests

2 participants