Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/neo-hack/actions-template
a fork version of typescript-action, self use.
https://github.com/neo-hack/actions-template
actions
Last synced: 16 days ago
JSON representation
a fork version of typescript-action, self use.
- Host: GitHub
- URL: https://github.com/neo-hack/actions-template
- Owner: neo-hack
- License: mit
- Created: 2021-10-05T15:14:07.000Z (over 3 years ago)
- Default Branch: master
- Last Pushed: 2023-02-11T12:26:57.000Z (about 2 years ago)
- Last Synced: 2024-11-14T14:10:46.339Z (3 months ago)
- Topics: actions
- Language: TypeScript
- Homepage:
- Size: 166 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
README
# @aiou/actions-template
*a fork version of [typescript-action](https://github.com/actions/typescript-action), self use*
[](https://github.com/spring-catponents/actions-template) [](https://github.com/spring-catponents/actions-template) [](https://github.com/spring-catponents/actions-template)
[Edit on StackBlitz ⚡️](https://github.com/spring-catponents/actions-template)
Use this template to bootstrap the creation of a Typescript action.:rocket:
This template includes tests, linting, a validation workflow, publishing, and versioning guidance.
## features
- 💪 Typescript - type safe
- 🦋 Changeset - modern changelog/version tool
- 📦 pnpm - much faster than yarn and npm
## development
Setup environment(if actions rely on environment)
1. copy `.env.sample` file to `.env`
2. replace with real environment
Most toolkit and CI/CD operations involve async operations so the action is run in an async function.
```javascript
const core = require('@actions/core');
...
async function run() {
try {
...
}
catch (error) {
core.setFailed(error.message);
}
}
run()
```
See the [toolkit documentation](https://github.com/actions/toolkit/blob/master/README.md#packages) for the various packages.
### change action.yml
The action.yml defines the inputs and output for your action.
Update the action.yml with your name, description, inputs and outputs for your action.
See the [documentation](https://help.github.com/en/articles/metadata-syntax-for-github-actions)
### publish
GitHub Actions will run the entry point from the action.yml. Packaging assembles the code into one file that can be checked in to Git, enabling fast and reliable execution and preventing the need to check in node_modules.
Actions are run from GitHub repos. Packaging the action will create a packaged action in the dist folder.
Run `build`
```bash
pnpm run build
```
Since the packaged index.js is run from the dist folder.
```bash
git add dist
```
### release
Users shouldn't consume the action from master since that would be latest code and actions can break compatibility between major versions.
Checkin to the v1 release branch
```bash
git checkout -b v1
git commit -a -m "v1 release"
```
```bash
git push origin v1
```
Note: We recommend using the `--license` option for ncc, which will create a license file for all of the production node modules used in your project.
Your action is now published! :rocket:
See the [versioning documentation](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md)
## usage
You can now consume the action by referencing the v1 branch
```yaml
uses: /@v1
with:
milliseconds: 1000
```
See the [actions tab]() for runs of this action! :rocket:
#
*built with ❤️ by 😼*