• Features
• Inputs
  • Permissions
• Outputs
• Examples
• Tags
• Support
• Contributing

JavaScript Action Template using Rollup.

• JavaScript: https://github.com/smashedr/javascript-action
• TypeScript: https://github.com/smashedr/typescript-action
• Dockerfile Python: https://github.com/smashedr/py-test-action
• Dockerfile Python UV: https://github.com/smashedr/test-action-uv
• Docker Image Python: https://github.com/smashedr/docker-test-action

This action creates or updates the provided tag to the sha has that triggered the workflow.

This includes inputs, outputs, job summary, and automatic token authentication.

With no inputs this will create/update the tag test.

- name: 'JavaScript Action'
  uses: smashedr/javascript-action@master

With all inputs.

- name: 'JavaScript Action'
  uses: smashedr/javascript-action@master
  with:
    tag: test
    summary: true
    token: ${{ secrets.PAT }} # only include this if you need to use a PAT

This action requires the following permissions:

permissions:
  contents: write

Permissions documentation for Workflows and Actions.

- name: 'JavaScript Action Template'
  id: test
  uses: smashedr/javascript-action@master
  with:
    tag: test

- name: 'Echo Output'
  run: |
    echo "sha: '${{ steps.test.outputs.sha }}'"

💡 Click on an example heading to expand or collapse the example.

name: 'Test'

on:
  workflow_dispatch:
  push:

jobs:
  test:
    name: 'Test'
    runs-on: ubuntu-latest
    timeout-minutes: 5
    permissions:
      contents: write

    steps:
      - name: 'Checkout'
        uses: actions/checkout@v6

      - name: 'JavaScript Action'
        id: test
        uses: smashedr/javascript-action@master

      - name: 'Echo Outputs'
        run: |
          echo "sha: '${{ steps.test.outputs.sha }}'"

For more examples, you can check out other projects using this action:
https://github.com/smashedr/javascript-action/network/dependents

The following rolling tags are maintained.

Version Tag	Rolling	Bugs	Feat.	Name	Target	Example
	✅	✅	✅	Major	vN.x.x	vN
	✅	✅	❌	Minor	vN.N.x	vN.N
	❌	❌	❌	Micro	vN.N.N	vN.N.N

You can view the release notes for each version on the releases page.

The Major tag is recommended. It is the most up-to-date and always backwards compatible. Breaking changes would result in a Major version bump. At a minimum you should use a Minor tag.

If you run into any issues or need help getting started, please do one of the following:

• Report an Issue
• Q&A Discussion
• Request a Feature
• Chat with us on Discord

If you would like to submit a PR, please review the CONTRIBUTING.md.

Please consider making a donation to support the development of this project and additional open source projects.

Additionally, you can support other GitHub Actions I have published:

• Stack Deploy Action
• Portainer Stack Deploy Action
• Docker Context Action
• Actions Up Action
• Rhysd Actionlint Action
• Zensical Action
• VirusTotal Action
• Homebrew Action
• Mirror Repository Action
• Update Version Tags Action
• Docker Tags Action
• TOML Action
• Update JSON Value Action
• JSON Key Value Check Action
• Parse Issue Form Action
• Cloudflare Purge Cache Action
• Mozilla Addon Update Action
• Package Changelog Action
• NPM Outdated Check Action
• Label Creator Action
• Algolia Crawler Action
• Create Pull Action
• Upload Release Action
• Check Build Action
• Web Request Action
• Get Commit Action

For a full list of current projects visit: https://cssnr.github.io/