Automatically restore to upstream when files are not modified in downstream
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 11
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 3
Description
Currently we pass an input restore-upstream to rhobs/syncbot/.github/workflows/merge-flow.yaml@main which helps the merge workflow to restore contents on conflict. This is not scalable as it keeps changing between latest merges. It would be better to find automatically upstream only files and restore on conflict.
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 with .github/workflows/merge-flow.yaml@main and trace how the restore-upstream input is used during conflict handling. Identify how the workflow could distinguish files changed only upstream from files modified downstream. Done means upstream-only files are restored automatically without changing a merge-specific input.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100