You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine Github is down and Action workflows aren’t available, and you want to publish the next release of your package… 😳
We currently still have small blobs of code in our Action workflows that could move into the Makefile. The goal of this exercise is to be able to use the Makefile locally and be able to build and publish a package release locally. The Action workflows should then simply use these Makefile goals, too.
Here’s a list of new Makefile goals we can consider:
Imagine Github is down and Action workflows aren’t available, and you want to publish the next release of your package… 😳
We currently still have small blobs of code in our Action workflows that could move into the Makefile. The goal of this exercise is to be able to use the Makefile locally and be able to build and publish a package release locally. The Action workflows should then simply use these Makefile goals, too.
Here’s a list of new Makefile goals we can consider:
make dist-hash
python-package-template/.github/workflows/_build.yaml
Lines 107 to 122 in 0b40f48
make release
python-package-template/.github/workflows/release.yaml
Lines 65 to 74 in 0b40f48
make release-publish
python-package-template/.github/workflows/release.yaml
Lines 148 to 167 in 0b40f48
make release-gh
python-package-template/.github/workflows/release.yaml
Lines 134 to 146 in 0b40f48
python-package-template/.github/workflows/release.yaml
Lines 213 to 216 in 0b40f48
The _release-notifications.yaml and _wiki-documentation.yaml Actions, in their entirety, could also be hoisted into the Makefile and be made part of the release.
The text was updated successfully, but these errors were encountered: