gravitational / gravitational/shared-workflows
Improve bot UX on failed backport
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 4
- Avg merge
- 19h 53m
- Merged PRs (30d)
- 5
Description
In the event that a backport fails due to conflicts, can we provide some commands/a script that can be run locally that performs the same steps as the bot, but allows for a human to resolve the conflicts that occurred.
Example of a failed run due to conflicts:
https://github.com/gravitational/teleport/runs/6279118931?check_suite_focus=true
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
Start by reviewing the failed backport run linked in the issue and the shared-workflows backport process. Identify the bot's steps and define a local command or script that reproduces them while allowing a human to resolve conflicts. Done means the local process can complete a conflicted backport and matches the bot's successful behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100