Commit graph

4 commits

Author SHA1 Message Date
Martin Pitt
2a51e057d7 Show how to run the release in GitHub workflow
Enter the new world of GitHub actions [1]/GitLab pipelines [2]. This
simplifies our end of the infrastructure considerably:

* No need any more to set up webhooks, all the relevant configuration
  is right in the workflow file.

* Does not need any infrastructure on our side any more, and thus works
  for third-party projects. They just need to set up their own secrets.

* GitHub automatically provides a temporary `GITHUB_TOKEN` with
  sufficient write access to the project to publish a release, so we
  don't need to carry around that secret. Thus if your project only
  releases to GitHub, there is zero secrets management.

Also adjust cockpituous-release a bit (update Fedora version, fix
project name copy-pasta), point to the action workflow and necessary
secrets.

Closes #380
2020-10-13 09:37:35 +02:00
Martin Pitt
acc7de2d6d cockpituous: Fix srpm Release:
Use release-srpm's `-V` option [1] so that the generated srpm will get a
proper changelog and Release "1" instead of "2".

[1] abb2bdb5

Closes #184
2019-06-12 09:54:42 +02:00
Martin Pitt
da06135330 cockpituous-release: Show how to do Fedora uploads
Closes #40
2018-08-28 22:51:10 +02:00
Martin Pitt
509547f502
Add minimal Cockpituous release script
This only builds a tarball and srpm, and shows a few other example.
Document the intent and point to the cockpituous docs.

Closes #37
2018-07-19 09:22:45 +02:00