Skip to content

Change development policy to repackaging on every code change #16

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

Merged
merged 4 commits into from
May 6, 2021

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented May 6, 2021

The previous development policy was to only repackage on each release. This prevented contributors from doing casual beta
testing by simply referencing the action as arduino/setup-taskfile@main in a workflow.

This policy change is implemented via:

  • Update development and release workflow documentation.
  • Add a CI job to check for forgotten packaging.
  • Repackage the current code.
  • Adjust the integration testing workflow to account for new policy.

per1234 added 4 commits May 5, 2021 21:46
The previous development policy was to only repackage on each release. This prevented contributors from doing casual beta
testing by simply referencing the action as `arduino/setup-taskfile@main` in a workflow.
In order to allow beta testing, it is necessary to package the action after every change to the code. This is an easy
step to forget, so an automated check is necessary.
Bring the action code up to sync with the source
Building will now be done in the same commit as the changes to the source code, so doing it in the integration test
workflow is pointless, only making the CI slower and the maintenance burden greater.
@per1234 per1234 added topic: documentation Related to documentation for the project type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels May 6, 2021
@per1234 per1234 requested review from silvanocerza, umbynos and rsora May 6, 2021 05:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: documentation Related to documentation for the project topic: infrastructure Related to project infrastructure type: enhancement Proposed improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants