Description of the need
I created two PRs a few months ago, and was waiting for them to get attention. It wasn't until yesterday I by chance saw this, under https://github.com/backdrop/backdrop#developers:
When submitting a pull request, please make sure there is an open issue in the issue tracker and reference it in the description on the pull request.
Proposed solution
Emphasize that PRs need a corresponding issue. Perhaps for PRs, a pull_request.md template could be made, with something like this?
## Description of the Pull Request
A short description of what the PR solves.
## Link to the issue
When submitting a pull request, please make sure there is an open issue in the issue tracker and reference it in this format (replace ISSUE_NUMBER):
Fixes: https://github.com/backdrop/backdrop-issues/issues/ISSUE_NUMBER
As a follow up task, maybe existing PRs could be scanned for missing issue references? It would be sad if too many first time contributors have PRs gathering dust for months or even years ...
Remaining Tasks
- [ ] Create a PR template
- [ ] Find existing PRs without a reference issue and add a comment to alert the creator of this requirement
Recent comments
For our DEV meeting: an older bug needs (and could have) a fix. Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All There are 2 pull requests, but one...
February 26th, 2026 - Weekly Meetings
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5