- Notifications
You must be signed in to change notification settings - Fork70
A Collection of GitHub Actions
License
marvinpinto/actions
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Generating release notes & automatically maintaining releases was much needed when GitHub Actions launched many years ago, but our ecosystem has evolved and there are much better alternatives these days.
For example, thesemantic-release project + their associatedGitHub Action gives you full control over when releases occur, changelog formatting, custom exec scripts, and much more. Another popular option is theaction-gh-release which also allows you to do many of the things this project originally enabled.
GitHub Actions give you the flexibility to build out automated software development lifecycle workflows directly in your repository. Aside from building your own actions, the framework also allows you to use pre-built actions made by other developers.
This repository is a collection of said actions which you are free to re-use and modify!
- GitHub Automatic Releases - automatically upload assets, generate changelogs, pre-releases, and so on.
The following actions are deprecated and no longer actively maintained. We are currently looking for maintainers to take over these projects. If you are interested in contributing or becoming the new maintainer, please check out theGitHub issue here.
- Keybase Notifications - send GitHub notifications to Keybase Chat channels, teams, and DMs.
- SSM Build Secrets - inject AWS SSM Parameter Store secrets as environment variables into your GitHub Actions builds.
You will first of all need a recent enough version ofnode as well asyarn. The node version used to build & test this project can be foundhere. Thescripts section under the rootpackage.json is a good place to get started.
yarn installyarn buildyarn lintyarntestyarn lintfix# automatic lint-fixing, during developmentJEST_VERBOSE=yes yarntest# useful for test output debugging
If you run into a issue you wish to report, it becomes a lot easier to trace the cause if debug logs are made available. You canenable debug logs in your GitHub repository by setting theACTIONS_STEP_DEBUG secret totrue.
After enabling debug logging you can link to the log in your issue. For private repositories you have the option of including the raw text log, or securely messaging it to me throughkeybase.
The source code for this project is released under theMIT License. This project is not associated with GitHub.
About
A Collection of GitHub Actions