| Filename | Latest commit message | Latest commit date |
|---|---|---|
|
|
||
| CODEOWNERS/.github | ||
| issue-templates/.github/ISSUE_TEMPLATE | ||
| pull-request-template/.github | ||
| rust-ci/.github/workflows | ||
| rust-create-release-with-assets/.github/workflows | ||
| rust-create-release-without-assets/.github/workflows | ||
| README.md | ||
github-actions
This repo contains a few useful Github actions that can be used for a self
hosted Github instance.
CODEOWNERS
The term "code owners" refers to individuals or teams specified in a repository who are responsible for maintaining certain files or directories within the project. When changes are proposed to those areas, the designated code owners are automatically requested for review. This ensures that the right people, who are most familiar with the specific parts of the code the changes are referencing, are involved in the decision-making and review process.
See CODEOWNERS/.github/CODEOWNERS file for an example with one user for *.
CODEOWNERS file should be placed in .github located in repo root.
Check out https://help.github.com/articles/about-codeowners/ for more details.
rust-create-release-with-assets
This action generates a new release with assets for Windows/Mac OS and
GNU/Linux. This action is executed when a new tag is pushed. A valid write token needs to be added to repo with the name WRITE_TOKEN (${{
secrets.WRITE_TOKEN }}). This token should have Contents (Read/Write)
permission set.
rust-create-release-without-assets
This action generates a new release without assets. This action is executed
when a new tag is pushed. A valid write token needs to be added to repo with
the name WRITE_TOKEN (${{ secrets.WRITE_TOKEN }}). This token should have
Contents (Read/Write) permission set.
rust-ci
This action builds, tests and checks formatting with rustfmt when pushing to
main branch.