https://github.com/dplocki/special-octo-potato

My balasting field for Github Actions. The place to test workflows, actions their result.
https://github.com/dplocki/special-octo-potato

git github-actions github-actions-test github-test github-workflows github-workflows-test sandbox test

Last synced: about 1 month ago
JSON representation

My balasting field for Github Actions. The place to test workflows, actions their result.

• Host: GitHub
• URL: https://github.com/dplocki/special-octo-potato
• Owner: dplocki
• Created: 2020-05-28T18:03:26.000Z (over 4 years ago)
• Default Branch: master
• Last Pushed: 2024-06-28T18:25:31.000Z (6 months ago)
• Last Synced: 2024-06-28T19:43:04.859Z (6 months ago)
• Topics: git, github-actions, github-actions-test, github-test, github-workflows, github-workflows-test, sandbox, test
• Language: Python
• Homepage:
• Size: 101 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# 🥔 Special Octo Potato

This is my blasting field for Github Actions. The place to test workflows, actions their result.

## Notes

* Official help for [GitHub Actions](https://help.github.com/en/actions)

* You cannot use the `alpine` image as `runs-on`

  * The only available options can be found on the page: [Virtual Environments for GitHub-hosted Runners](https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners)

  * You can use a Docker image

* Job names must start with a letter or `_` and contain only alphanumeric characters, `-`, or `_`

* You can react to tags without declaring the branch

* If you have a syntax error in your workflow file, you lose access to the history of previous builds for that workflow

* The workflow must contain at least one job with no dependencies

* If the cron schedule contains a slash `/` character, it needs to be in quotes

* Scheduled tasks seem to have some delay in starting

* The difference between `github.ref_name` and `GITHUB_REF` while dealing with tag: one return only the tag name, the other the full tag name (with prefix)

### Github NPM Packages

There is possibility for publish npm packages directly on Github (as not scoped repository). See [GitHub Packages: Your packages, at home with their code](https://npm.pkg.github.com).

The usage in workflow is described here: [Publishing Node.js packages](https://docs.github.com/en/actions/guides/publishing-nodejs-packages).

Example set-up code:

```yml

      - name: "Set up the NPM"

        uses: actions/setup-node@v2

        with:

          node-version: '16'

          registry-url: 'https://npm.pkg.github.com'

          scope: '@dplocki'

```

Later usage:

```yml

      - name: "Compering version"

        run: |

          echo `npm info @dplocki/generic-conversation-bot version`

        env:

          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

```

### Create tag

```yml

      - name: Create Tag

        uses: negz/create-tag@v1

        with:

          version: v0.1.1

          message: Release for version v0.1.1

          token: ${{ secrets.GITHUB_TOKEN }}

```

## Multiline scripts in YML

```yml

  run: |

    cat << EOF > run.py

    echo line 1

    echo line 2

    ; no indents on each of this lines

    EOF

```

## Links

* [GitHub Actions to securely publish npm packages](https://snyk.io/blog/github-actions-to-securely-publish-npm-packages/)