Don't unconditionally allow pushing to other people's stacks
Open
Nobody has claimed this yet.
papercut
- Dominant language
- Python
- Stars
- 1k
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Description
Probably should require you to set some flag first before we are willing to push over it
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
No file, test, or command entry point is named. Start by tracing ghstack's push workflow and how it identifies stack ownership; determine where an explicit opt-in flag and the rejection behavior should be defined. Done means pushing over another user's stack is blocked by default and permitted only when the flag is set, with tests covering both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100