-
Notifications
You must be signed in to change notification settings - Fork 3
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
Simplify Workflows #136
Comments
If workflows are >90% the same for all curricula, this sounds like the most feasible option to me |
They are all 100% identical. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is possible to reuse workflows in GitHub Actions (see here for more info).
We could create two reusable workflows, one that takes care of checking out code and building the files, and one that creates the actual release (candidate).
Our three main Workflows (build main/release, build pr, and build release candidate) can then reuse these two new workflows, resulting in a cleaner structure of the main workflows, whilst also reducing duplicate code.
We could also consider to move them all to a separate repository and use them from all other repositories.
The text was updated successfully, but these errors were encountered: