Skip to content

Commit

Permalink
Merge pull request #6 from local-ch/create-action
Browse files Browse the repository at this point in the history
Introduce Calculate Namespace Action
  • Loading branch information
cedricwider committed Mar 12, 2021
2 parents 3cf7c1f + 28b21d6 commit 3cc1d27
Show file tree
Hide file tree
Showing 14 changed files with 5,342 additions and 8,837 deletions.
10 changes: 7 additions & 3 deletions .github/workflows/test.yml
Expand Up @@ -11,14 +11,18 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: actions/setup-node@v2
with:
node-version: 14
- run: |
npm install
yarn install
- run: |
npm run all
yarn all
test: # make sure the action works on a clean machine without building
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: ./
with:
milliseconds: 1000
app: 'test_app_name'
branch: 'test-branch-name'
110 changes: 14 additions & 96 deletions README.md
@@ -1,105 +1,23 @@
<p align="center">
<a href="https://github.com/actions/typescript-action/actions"><img alt="typescript-action status" src="https://github.com/actions/typescript-action/workflows/build-test/badge.svg"></a>
</p>
# Calculate Deployment Name Action

# Create a JavaScript Action using TypeScript
Github Action to unify and centralize calculating deployment names for all
github actions.

Use this template to bootstrap the creation of a TypeScript action.:rocket:

This template includes compilation support, tests, a validation workflow, publishing, and versioning guidance.
## Motivation

If you are new, there's also a simpler introduction. See the [Hello World JavaScript Action](https://github.com/actions/hello-world-javascript-action)
To prevent every author of every application that uses github actions, to copy
the line where we calculate the deployment name across several files, we decided
to use a centralized approach, so all applications will work with the same
pattern of deployment names, no matter what stack they're written in.

## Create an action from this template
## Usage

Click the `Use this Template` and provide the new repo details for your action

## Code in Main

> First, you'll need to have a reasonably modern version of `node` handy. This won't work with versions older than 9, for instance.
Install the dependencies
```bash
$ npm install
```

Build the typescript and package it for distribution
```bash
$ npm run build && npm run package
```

Run the tests :heavy_check_mark:
```bash
$ npm test

PASS ./index.test.js
✓ throws invalid number (3ms)
wait 500 ms (504ms)
test runs (95ms)

...
```

## Change action.yml

The action.yml contains 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)

## Change the Code

Most toolkit and CI/CD operations involve async operations so the action is run in an async function.

```javascript
import * as core from '@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.

## Publish to a distribution branch

Actions are run from GitHub repos so we will checkin the packed dist folder.

Then run [ncc](https://github.com/zeit/ncc) and push the results:
```bash
$ npm run package
$ git add dist
$ git commit -a -m "prod dependencies"
$ git push origin releases/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)

## Validate

You can now validate the action by referencing `./` in a workflow in your repo (see [test.yml](.github/workflows/test.yml))
Basic:

```yaml
uses: ./
with:
milliseconds: 1000
- uses: localsearch/calculate-deployment-name-action@v1
with:
app: ${{github.event.repository.name}}
branch: ${{ github.head_ref }}
```

See the [actions tab](https://github.com/actions/typescript-action/actions) for runs of this action! :rocket:

## Usage:

After testing you can [create a v1 tag](https://github.com/actions/toolkit/blob/master/docs/action-versioning.md) to reference the stable and latest V1 action
28 changes: 0 additions & 28 deletions __tests__/main.test.ts

This file was deleted.

14 changes: 8 additions & 6 deletions action.yml
@@ -1,11 +1,13 @@
name: 'Your name here'
description: 'Provide a description here'
author: 'Your name or organization here'
name: 'Calculate Deployment Name'
description: 'Calculates valid deployment names based on repo name and branch name'
author: 'localsearch'
inputs:
milliseconds: # change this
app: # change this
required: true
description: 'input description here'
default: 'default value if applicable'
description: 'Application name (usually repo name)'
branch:
required: true
description: 'Name of the current branch'
runs:
using: 'node12'
main: 'dist/index.js'
529 changes: 491 additions & 38 deletions dist/index.js

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion dist/index.js.map

Large diffs are not rendered by default.

23 changes: 23 additions & 0 deletions dist/licenses.txt

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

0 comments on commit 3cc1d27

Please sign in to comment.