-
Notifications
You must be signed in to change notification settings - Fork 56
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
Automatic release generation through Github actions #193
base: main
Are you sure you want to change the base?
Conversation
Is there anything I need to change or think about, or is it all handled automatically? I don't know much about Github workflow. |
I've just realized you can delete sync-fork.yml. You will not need this workflow obviously. The release process is in two stages:
With the current configuration, the first stage is run on every push on every branch (to see if building and compiling still works). Other tests could be included here. The resulting files will only be attached as artifacts to the build and automatically deleted after some days. For all pushes to the main branch, both stages are run, so it will also actually publish the packages from the first phase. In release.yml, lines 3-6, this is the configuration for when to run the first phase:
It also gives you a button in Github Actions to manually trigger a build (for testing). You can also comment the "push:" line to have it only on button press. Please note that the button only appears in Github Actions if you have the workflow in your main branch. This is a limitation of Github. Other triggers like "push:" will also work from any branch. The second phase is limited to the main branch in lines 44-45:
You probably want to set Please note that releases contain a date tag and are updated if you have multiple commits per day to the main branch. The configuration for releases is line 48-55 in release.yml. Let me know if you have further questions. |
eaf9fc6
to
05d79c9
Compare
529e82b
to
4e734a0
Compare
* Add Makefile * Add libadwaita submodule * Add release workflow * Add Debian & RPM package building
a64af5b
to
d2ed145
Compare
d2ed145
to
5a15b84
Compare
5a15b84
to
b3089fd
Compare
6b57282
to
3145229
Compare
0f0b8a6
to
ed35999
Compare
* Add Makefile * Add libadwaita submodule * Add release workflow * Add Debian & RPM package building
ed35999
to
b912517
Compare
Hey, I am not sure if you are interested in this.
I've built a Github workflow to automatically generate a release including pulling in GTK4 CSS from libadwaita and including a Debian package.
As a next step, I plan to publish those releases on a PPA so they can easily be installed and automatically updated.