Any way to allow blurb_it to write to other people's pending cpython PRs?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 33
- Forks
- 22
- Avg merge
- 23m
- Merged PRs (30d)
- 2
Description
I was hoping to use the we blurb_it to write a NEWS entry for someone's PR that currently lacked one while reviewing it. Unfortunately only appear to be able to grant it access to my own cpython fork rather than PR branches in other people's forks.
Obviously I can't grant it blanket write access to everything I have access to so I'm not sure there is anything that can be done about this. I'm just filing the issue to as a 🦄 "wouldn't it be nice if" 🦄 idea.
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.
Research direction
Start by reviewing blurb_it's current authorization behavior for writing NEWS entries to cpython pull requests and compare it with permissions for a user's own fork. Define whether safely granting access to another contributor's PR branch is feasible without blanket repository access. Done means a documented, secure approach or a clear explanation of why the capability cannot be supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100