Skip to content
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

packit: only use IoT relevant branches #156

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

miabbott
Copy link
Member

Since IoT uses a rolling stable ref, we don't need action on the n-1 "stable" branch in Fedora dist-git. (i.e. stable is currently F40, we don't need action on the F39 branch)

Packit has some aliases that let us narrow the scope of versions that the service will operate against. fedora-development targets the next major version of Fedora + Rawhide. fedora-latest-stable targets exactly one version (the latest version) of stable. See below:

>>> from packit.config.aliases import get_aliases
>>> get_aliases()['fedora-development']
['fedora-41', 'fedora-rawhide']
>>> get_aliases()['fedora-latest-stable']
['fedora-40']

Since IoT uses a rolling `stable` ref, we don't need action on the n-1
"stable" branch in Fedora dist-git. (i.e. stable is currently F40, we don't
need action on the F39 branch)

Packit has some aliases that let us narrow the scope of versions that
the service will operate against. `fedora-development` targets the
next major version of Fedora + Rawhide. `fedora-latest-stable`
targets exactly one version (the latest version) of stable. See below:

```
>>> from packit.config.aliases import get_aliases
>>> get_aliases()['fedora-development']
['fedora-41', 'fedora-rawhide']
>>> get_aliases()['fedora-latest-stable']
['fedora-40']
```

Signed-off-by: Micah Abbott <miabbott@redhat.com>
@say-paul
Copy link
Member

LGTM

@say-paul say-paul merged commit 74dd761 into fedora-iot:main Sep 23, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants