RFC: Use GH-labels to flag a PR that has [noissue] or multiple commits
Open
Nobody has claimed this yet.
stale
- Dominant language
- Python
- Stars
- 10
- Forks
- 40
- Avg merge
- 21h 24m
- Merged PRs (30d)
- 8
Description
The idea is that the PR CI can set (clear) labels about the state of the commits.
- noissue in case, any commit message contains
[noissue]- reviewers should take extra care if those commits are suitable for not having an issue - multi-commit in case the PR contains more than one commit - reviewers should judge if the changes suitable to be split into seperate commits, and occasionally request to split the PR or merge the commits
Simple PR's would not have these labels.
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
The payload names no files; start by locating the repository's pull-request CI configuration and how it inspects commit messages and applies labels. Verify the [noissue] and multi-commit conditions against representative pull requests, including simple single-commit PRs, and confirm labels are set or cleared as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100