Automatic feature branch updates include the same conflicts week over week
Open
@elookpotts-nvidia is already working on this.
Since Feb 4, 2026.
bug
- Dominant language
- Python
- Stars
- 260
- Forks
- 57
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 69
Description
Describe the bug.
For example:
- https://github.com/NVIDIA/OSMO/pull/280/changes/640c1e1e7b12a14065693fda2c37f7d1151e3e42
- https://github.com/NVIDIA/OSMO/pull/286/changes/5da311d90769e8b1f3c0bc69e8076b2f461d8ca3
- https://github.com/NVIDIA/OSMO/pull/349/changes/0486c3263e7a9ef1caea16ae84b615d5b1dcf1a9
Minimum reproducible example
Relevant log output
Environment
- Kubernetes version
- OSMO version
- Scheduler version
- Cloud provider or hardware configuration
- Anything else that is relevant
Code of Conduct
- I agree to follow NVIDIA OSMO's Code of Conduct
- I have searched the open bugs and have found no duplicates for this bug report
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.
Assessment
This issue has not been assessed yet.