Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Allow multiple branches #1379

Open
AMDmi3 opened this issue Feb 9, 2024 · 0 comments
Open

Allow multiple branches #1379

AMDmi3 opened this issue Feb 9, 2024 · 0 comments
Labels

Comments

@AMDmi3
Copy link
Member

AMDmi3 commented Feb 9, 2024

Consider the following upstream versions:
2.0.0, 1.2.0, 1.1.1, 1.1.0, 1.0.1, 1.0.0

Consider the following repository versions:
2.0.0, 1.1.1. 1.0.0

With setbranchcomps: 1, 1.1.1 is outdated (since there's newer 1.2.0 in the 1.x branch), but 1.0.0 is not.
With setbranchcomps: 2, 1.0.0 is outdated (since there's newer 1.0.1 in 1.0.x branch), but 1.1.1 is not.

However, we probably want to mark both versions outdated, so setbranchcomps: 2 should generate two branches (and there should be support for multiple branches as well).

@AMDmi3 AMDmi3 added the bug label Feb 9, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant