Do you intend to support sending the status to a specific commit?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 18
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
This issue has no description.
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 provides no files, tests, or acceptance criteria. Start by locating the code that sends build status to Git providers, then clarify which providers and expected behavior are in scope before defining tests for associating a status with a specific commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100