LizardByte actions

Reusable actions for GitHub workflows.

actions

Action	Description	Type	Language
artifact_comment	Post workflow artifact links in a sticky pull request comment	composite	javascript
audit_repos	Audit repositories in an organization	composite	javascript
facebook_post	Post to Facebook page/group using Graph API	docker	python
get_changed_files	Get the list of changed files in a pull request	composite	javascript
monitor_space	Monitor and track minimum free disk space	composite	bash
pinact	Run pinact against repositories in an organization and create PRs for updates	composite	javascript
more_space	Free up disk space in GitHub Actions runners	composite	bash
release_changelog	Generate a changelog for the latest release	composite	javascript
release_create	Create a new release	composite	bash, javascript
release_homebrew	Validate and update Homebrew formula	composite	bash, python
release_setup	Prepare a release	docker	python
screenshot	Setup cross-platform screenshot CLI tool	composite	bash
setup_cuda	Set up NVIDIA CUDA Toolkit on Linux runners	composite	bash
setup_python	Set up Python environment	composite	bash
trailing_spaces	Check files for trailing spaces, empty lines at EOF, and missing newline at EOF	composite	javascript
virtual_desktop	Setup virtual desktop for GUI apps on Linux	composite	bash

Contributions

Contributions are welcome! See our Contributor's Guide.

Patterns

Workflows

This repo has two workflows to test the actions:

• ci.yml
  • A matrix is generated for each action based on the ci-matrix.json file in the action's directory. To add or remove a matrix, edit the ci-matrix.json file.
  • Each action should have at least one matrix defined.
  • If anything needs run before the action is run, create a pre-ci.sh file in the action's directory.
  • If anything needs run after the action is run, create a post-ci.sh file in the action's directory.
• ci-tests.yml
  • This workflow runs unit tests for the repo using pytest and Jest.
  • Tests should 100% cover JavaScript and Python code.

Action Types

This repo has two types of actions:

• Docker: These actions are run in a Docker container. They should have a Dockerfile in the action's directory.
• Composite: These actions are run as a series of steps in the workflow.

Additional action types can be used if necessary.

Action Languages

This repo has three languages used for actions:

• Bash: Used in portions of composite actions.
• JavaScript: Used in portions of composite actions.
• Python: Used in Docker actions and composite actions.

Additional languages can be used if necessary.

License

This repository is licensed under the MIT License. Individual actions may be licensed under a different license if specified in their respective directories.