sanitizers / sanitizers/patchback-github-app
[idea] Trigger a `repository_dispatch` or a `workflow_dispatch` upon backport completion
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 14
- Forks
- 10
- Avg merge
- 4m
- Merged PRs (30d)
- 3
Description
It just occurred to me that some workflows might benefit from such a callback. Maybe, we could even report failure/timeout, not just success.
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 files, tests, or entry points are named. Start by locating the backport-completion flow and reading GitHub's repository_dispatch and workflow_dispatch documentation. Define whether callbacks cover success, failure, and timeout, and specify the event payload and completion conditions before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions, python
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100