Pull requests: size and risk labels, and a limit on open pull requests for new contributors
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github-actions, python
- Domain
- ci-cd, devtools, documentation
Research direction
Start by reading the existing GitHub workflows, pull request template, and CONTRIBUTING file; identify how pull request checks and labels are currently configured. Check the repository’s core paths named in the issue and how GitHub handles open-pull-request limits for users without write access. Done means new pull requests receive size labels, high-risk cases are labeled, the limit and testing prompt are addressed, and CONTRIBUTING explains the labels.
Written by the indexing model from the issue text.
Description
What needs doing
- A label for the size of a pull request (
size/Stosize/XL). - A
risk:highlabel, set automatically when a pull request touches
the core paths (the agent loop, the tool handlers, the guards, the
workflows), is larger than about 400 lines, or comes from a
first-time contributor. - GitHub's limit on open pull requests for users without write
access. - The pull request template asks how the change was tested.
Why
Review time should go where a mistake costs most. Small, low-risk
changes should flow.
Done when
- Every new pull request gets a size label.
-
risk:highappears on a pull request that touches a core path. - CONTRIBUTING says what the labels mean.
- The pull request template has two more fields: a box to tick when AI tools helped write the change, and the line "I can explain every line of this change".
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 197
- Avg merge
- 16h 6m
- Merged PRs (30d)
- 168
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from inferstep/ATLAS
-
Bootstrap: the last two steps run as the user who owns the installMay be free again @assassinationss claimed this 11 days ago, and no pull request is open. Openarea/install reliability
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
inferstep/ATLAS#412 · 4 comments ·
Maintainers usually reply within 1 day
-
area/cli
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
area/cli area/lens status/ready
Difficulty 2/5 Half a day Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
area/ci status/ready
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
inferstep/ATLAS#245 · 4 comments ·
Maintainers usually reply within 1 day
-
area/sandbox security
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Maintainers usually reply within 1 day
Similar issues
-
idxmax/idxmin raise ValueError when a single partition is all-NAPossibly taken @Jason10191019999 claimed this today. Openneeds triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 3 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
[BUG]: Windows GUI package of v1.17.0-rc3 has no GTK DLLsPossibly taken @andrut-ds claimed this today. Openbug CI/CD Pactus-GUI Windows
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pactus-project/pactus#2428 ·
Maintainers usually reply within 1 day
-
DiskDataset.reshard() can hang with a zero or negative shard sizePossibly taken @Programmer-Develops claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 19 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
GNS3/gns3-server#3017 · 1 comment ·
Maintainers usually reply within 1 day