Skip to content

Latest commit

 

History

History
90 lines (52 loc) · 3.1 KB

CONTRIBUTING.md

File metadata and controls

90 lines (52 loc) · 3.1 KB
Raw

Development workflow

1. Install Tools

Task

Common development processes are run using the Task task runner tool.

Follow the installation instructions here:
https://taskfile.dev/#/installation

Node.js

npm is used for dependency management.

Follow the installation instructions here:
https://nodejs.dev/en/download

Node.js 20.x is used for development of this project. nvm is recommended to easily switch between Node.js versions.

Extras

Some optional tools used by this project:

2. Coding

Now you're ready to work some TypeScript magic!

Make sure to write or update tests for your work when appropriate.

3. Format code

Format the code to follow the standard style for the project:

npm run format

4. Run tests

Run the tests to ensure that the code works as expected:

task check

5. Build

It is necessary to compile the code before it can be used by GitHub Actions. Remember to run this command before committing any code changes:

task build

6. Commit

Everything is now ready to make your contribution to the project, so commit it to the repository and submit a pull request.

Thanks!

Dependency license metadata

Metadata about the license types of all dependencies is cached in the repository. To update this cache, run the following command from the repository root folder:

task general:cache-dep-licenses

The necessary Licensed tool can be installed by following these instructions.

Unfortunately, Licensed does not have support for being used on the Windows operating system.

An updated cache is also generated whenever the cache is found to be outdated by the by the "Check Go Dependencies" CI workflow and made available for download via the dep-licenses-cache workflow artifact.

Enable verbose logging for a pipeline

Additional log events with the prefix ::debug:: can be enabled by setting the secret ACTIONS_STEP_DEBUG to true.

See step-debug-logs for reference.

Release workflow

Instructions for releasing a new version of the action:

  1. If the release will increment the major version, update the action refs in the examples in README.md (e.g., uses: arduino/setup-task@v1 -> uses: arduino/setup-task@v2).
  2. Create a GitHub release, following the vX.Y.Z tag name convention. Make sure to follow the SemVer specification.
  3. Rebase the release branch for that major version (e.g., v1 branch for the v1.x.x tags) on the tag. If no branch exists for the release's major version, create one.