-
Notifications
You must be signed in to change notification settings - Fork 144
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
Split copr project into stable
and latest
#3375
Conversation
2372d93
to
bc7d176
Compare
release
and nightly
stable
and latest
bc7d176
to
f08b088
Compare
f08b088
to
525ab2e
Compare
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.
Thanks the simplification again. I've added a couple adjustments in 525ab2e. Mainly the hatch version
which is needed to keep copr builds newer than packages in Fedora repositories, plus some more comments and minor stuff.
@LecrisUT, @martinhoyer, could you please have a quick look if the changes are ok?
/packit build |
Let copr and packit decide the best format for the versions Signed-off-by: Cristian Le <[email protected]>
Add a couple more comments to the configuration. Update the installation documentation accordingly. Use `hatch version` so that copr builds are newer. Use `all_committers` instead of individual names.
525ab2e
to
5bcb8c9
Compare
/packit build |
Both failures seem to be related to inaccessible
Merging. |
This is a followup to #3374 requiring creation of 2 new copr projects
stable
andrelease
(mirroring the RTD configuration) which have the GH release builds andmain
branch builds respectively.This allows to simplify the
get-current-version
as we can simply use the packit defaults and not have to worry about the ordering. Inside each project the builds are guaranteed to be in appropriate order.