update-version.sh should use the release branch for abi-checker workflow
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
Research direction
Start with update-version.sh and the abi-checker GitHub Actions workflow, then compare the 26.08 example in pull request #2331. Verify that after a release branch is created, ABI comparison targets that release branch rather than main; done means the workflow uses the correct branch for the release process.
Written by the indexing model from the issue text.
Description
Fix the update-version.sh for the abi-checker actions workflow. Once the release branch is created, the ABI comparison should be done against the release branch and not main.
Example in 26.08: https://github.com/NVIDIA/cuvs/pull/2331
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 64
Contributor guide
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.
More from NVIDIA/cuvs
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
ci Lucene
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
willow
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openedx/openedx-authz#460 ·