Skip merge flow when the upstream latest tag is already merged on downstream
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 6
- Forks
- 11
- Avg merge
- 5d 9h
- Merged PRs (30d)
- 3
Description
This can be determined by calling the following api,
GET /repos/{owner}/{repo}/compare/{basehead}
e.g. openshift/thanos:master vs thanos-io/thanos:v0.22.0
curl -s https://api.github.com/repos/openshift/thanos/compare/{master}...{thanos-io:v0.22.0} -o - | jq .ahead_by
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 at the merge-flow entry point that decides whether downstream synchronization should run. Use the GitHub compare API shown in the issue and inspect its ahead_by result for the upstream latest tag versus downstream. Done means the merge flow is skipped when that tag is already merged; verify the comparison with the provided curl and jq example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100