-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow filtering tags via regex configuration options #2030
Allow filtering tags via regex configuration options #2030
Conversation
This comment was marked as outdated.
This comment was marked as outdated.
361452e
to
de76b69
Compare
de76b69
to
21b516c
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 29s |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since upstream_tag_template
is no longer used to filter tags, what happens with projects that rely on it? Should they migrate to upstream_tag_include
?
Edit: I mean projects/repos with mixed tag names that use upstream_tag_template
for both filtering and extracting version.
21b516c
to
1b2f0b1
Compare
Build succeeded. ✔️ pre-commit SUCCESS in 1m 26s |
Let me try to go through configs using |
@nforro for that the |
I used
That's 5 projects, https://github.com/evgeni/bley is not there because it doesn't actually use It would probably make sense to check if the "offending" tags are just historical and not a pattern that's still used. |
@lbarcziova Feel free to check yourself, maybe I missed something. |
1b2f0b1
to
2a9a9d8
Compare
Introduce 2 configuration options, upstream_tag_include and upstream_tag_exclude to allow filtering the tags. This will be used in the service to allow filtering the propose_downstream runs. Fixes packit/packit-service#2118
This comment was marked as outdated.
This comment was marked as outdated.
2a9a9d8
to
0154d12
Compare
@nforro thanks! I will check those and open PRs where needed once this lands in production |
Build succeeded. ✔️ pre-commit SUCCESS in 1m 44s |
Build succeeded (gate pipeline). ✔️ pre-commit SUCCESS in 1m 28s |
We have changed the behaviour of getting latest tags from the repository in Packit (packit/packit#2030) and therefore, for repositories with multiple versioning schemas, it is needed to add these options. For more details, see https://packit.dev/docs/configuration#upstream_tag_include
We have changed the behaviour of getting latest tags from the repository in Packit (packit/packit#2030) and therefore, for repositories with multiple versioning schemas, it is needed to add these options. For more details, see https://packit.dev/docs/configuration#upstream_tag_include
Introduce 2 configuration options, upstream_tag_include and upstream_tag_exclude to allow filtering the tags. This will be used in the service to allow filtering the propose_downstream runs.
Fixes packit/packit-service#2118
TODO:
packit/packit.dev
.RELEASE NOTES BEGIN
2 new configuration options for filtering when getting latest upstream release tag were introduced:
upstream_tag_include
andupstream_tag_exclude
. They should contain a Python regex that can be used as an argument inre.match
.RELEASE NOTES END