sanitizers / sanitizers/patchback-github-app
Expose the cherry-pick application conflict in the status updates
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 14
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 3
Description
This is what @jimi-c wished for, and I've been considering in the past.
UX things to explore:
- What are the limitations of the comment updates, attached files and Checks API updates?
- What's the level of detail we can have for both reporting interfaces? Should they differ?
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 names comment updates, attached files, and Checks API updates as the reporting interfaces; compare their limitations and supported detail first. Done means a decided UX approach for exposing cherry-pick conflicts and a clear choice of whether the interfaces should differ.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- api, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100