oxidecomputer / oxidecomputer/rfd-api
RFD branch for published RFD created new revision
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 95
- Forks
- 22
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 17
Description
We had a case today where a user accidentally created a branch for an RFD number which is already on the default branch in the published state. This should be a no-op and we should be ignoring the branch since it is not authoritative. In practice a new revision was created with the contents of the new branch.
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
The issue does not name a file, test, or entry point. Start by tracing the branch-processing path for RFDs already published on the default branch, then add or update a regression test showing that an accidental branch is ignored and no new revision is created.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100