Automation: point the source in new branches to the correct place
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
The issue only refers to Python issue 77105 and does not name a file, test, or entry point. Read that linked issue first to determine the intended source location for new branches, then inspect the release automation and verify branch creation uses the corrected location.
Written by the indexing model from the issue text.
Description
- Dominant language
- Python
- Stars
- 61
- Forks
- 48
- Avg merge
- 1h 22m
- Merged PRs (30d)
- 4
Contributor guide
No contributing guide indexed for this repository
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 python/release-tools
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
python/release-tools#401 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
python/release-tools#434 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
python/release-tools#417 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
python/release-tools#397 ·
-
bug
python/release-tools#286 · 1 assignee ·
All issues in python/release-tools
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
learningequality/ricecooker#747 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
run-llama/llama_index#23199 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
KhronosGroup/glTF-Blender-IO#2769 ·