Skip to content

Change development policy to continuous packaging #30

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 6 commits into from
Jan 10, 2022
Merged

Change development policy to continuous packaging #30

merged 6 commits into from
Jan 10, 2022

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Jan 6, 2022

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/arduino-lint-action@main in a workflow.

This policy change is implemented via:

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

This aligns the development policy of this project with that of the arduino/setup-task action, which has successfully used continuous packaging for some time now (arduino/setup-task#16).

The commands were prefixed by "#", evidently to indicate a command prompt. But that is the shell comment syntax, so it
is very unintuitive.
The development process for contributors follows a reasonably linear set of distinct steps, so this is an appropriate
way of organizing the information.
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/arduino-lint-action@main` in a workflow.
On every push and pull request that affects relevant files, check to make sure the ncc packaging is up to date.
Bring the action code up to sync with the source
Now that the development policy is to continuously package the project, and this policy is enforced by the CI workflow,
the action will always be pre-built, so building it again during the integration test workflow runs is pointless.
@per1234 per1234 added topic: documentation Related to documentation for the project type: enhancement Proposed improvement topic: infrastructure Related to project infrastructure labels Jan 6, 2022
@per1234 per1234 self-assigned this Jan 6, 2022
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