This action simplifies the GitHub release process by automatically uploading assets, generating changelogs, handling pre-releases, and so on. Original work by marvinpinto, updated and refactored by crowbarmaster. This action is fully compatable with marvinpinto's original work.

1. Usage Examples
2. Supported Parameters
3. Event Triggers
4. Versioning
5. How to get help
6. License

NOTE: The crowbarmaster/GH-automatic-releases repository is an automatically generated mirror of the crowbarmaster/GHactions monorepo containing this action. Please file issues and pull requests over there.

This example workflow will kick in as soon as changes land on master. After running the steps to build and test your project:

1. It will create (or replace) a git tag called latest.
2. Generate a changelog from all the commits between this, and the previous latest tag.
3. Generate a new release associated with the latest tag (removing any previous associated releases).
4. Update this new release with the specified title (e.g. Development Build).
5. Upload LICENSE.txt and any jar files as release assets.
6. Mark this release as a pre-release.

You can see a working example of this workflow over at crowbarmaster/GHactions.

---
name: "pre-release"

on:
  push:
    branches:
      - "master"

jobs:
  pre-release:
    name: "Pre Release"
    runs-on: "ubuntu-latest"

    steps:
      # ...
      - name: "Build & test"
        run: |
          echo "done!"

      - uses: "crowbarmaster/GH-Automatic-Releases@latest"
        with:
          repo_token: "${{ secrets.GITHUB_TOKEN }}"
          automatic_release_tag: "latest"
          prerelease: true
          title: "Development Build"
          files: |
            LICENSE.txt
            *.jar

Similar to the previous example, this workflow will kick in as soon as new tags are pushed to GitHub. After building & testing your project:

1. Generate a changelog from all the commits between this and the previous semver-looking tag.
2. Generate a new release and associate it with this tag.
3. Upload LICENSE.txt and any jar files as release assets.

Once again there's an example of this over at crowbarmaster/GHactions.

---
name: "tagged-release"

on:
  push:
    tags:
      - "v*"

jobs:
  tagged-release:
    name: "Tagged Release"
    runs-on: "ubuntu-latest"

    steps:
      # ...
      - name: "Build & test"
        run: |
          echo "done!"

      - uses: "crowbarmaster/GH-Automatic-Releases@latest"
        with:
          repo_token: "${{ secrets.GITHUB_TOKEN }}"
          prerelease: false
          files: |
            LICENSE.txt
            *.jar

The following output values can be accessed via ${{ steps.<step-id>.outputs.<output-name> }}:

• Parameters denoted with ** are required.
• The files parameter supports multi-line glob patterns, see repository examples.

The GitHub Actions framework allows you to trigger this (and other) actions on many combinations of events. For example, you could create specific pre-releases for release candidate tags (e.g *-rc*), generate releases as changes land on master (example above), nightly releases, and much more. Read through Workflow syntax for GitHub Actions for ideas and advanced examples.

Every commit that lands on master for this project triggers an automatic build as well as a tagged release called latest. If you don't wish to live on the bleeding edge you may use a stable release instead. See releases for the available versions.

- uses: "crowbarmaster/GH-Automatic-Releases@<VERSION>"

The main README for this project has a bunch of information related to debugging & submitting issues. If you're still stuck, try and get a hold of me on keybase and I will do my best to help you out.

The source code for this project is released under the MIT License. This project is not associated with GitHub.