Skip to content

Link to current queue in "new issue" message #46

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rixx
Copy link

@rixx rixx commented Jun 4, 2025

Noticed the bot message was missing the link in "you can see the current queue here". I took the link for the review queue from the README.

(FWIW I chose to include more than just “here” in the linked part to make it easier to click and more informative, but that’s just personal preference, can change it to just “here“, too.)

@rixx
Copy link
Author

rixx commented Jun 4, 2025

Oh humm, apparently the README links to the review queues aren’t actually correct, as they refer to labels that no longer exist. Let me fix that, too.

@rixx
Copy link
Author

rixx commented Jun 4, 2025

Hm. The project board columns don’t map cleanly to the review queues mentioned in the README – particularly, there is no way (or is there?) with the board to distinguish between the "Determining if this is expected in Django" review queue and the "Creating DEPs for expected features" review queue, as I don’t believe there is currently a tag or a project stage indicating that writing a DEP is the next step. (And maybe we can just drop that from the README then?)

Since having links that are somewhat working is (probably) still better than having links that refer to missing labels, I decided to link to the same view for both for now. For consistency, I linked to the project view on the "needs team" link as well, adding a filter for that label as well as filtering for project stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant