Proposal: Willing to add autorelease support to GitHub actions

[IgnorantSapient]

Hey @ignatk,

Based on your comment I understand that you want to add auto-release via GitHub actions, I am willing to help with this.

Here is how I am envisioning the workflow:

1. We use this action.
2. We add a CHANGELOG.md file to this repo.
3. Whenever a new version # is added to the CHANGELOG.md file in the master/main branch, a release is triggered.

If you have a different vision for the auto-release, please do share it with me.

Before we start doing this, we could also change the primary branch to main (If I recall correctly, you wanted to change master to main).

Let me know your thoughts.......

[IgnorantSapient]

Or we could do something similar to what's been done here:

name: Releases
on:
  push:
    branches:
      - main

jobs:
  changelog:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2

      - name: conventional Changelog Action
        id: changelog
        uses: TriPSs/conventional-changelog-action@v3.7.1
        with:
          github-token: ${{ secrets.CHANGELOG_RELEASE }}
          version-file: './package.json,./package-lock.json'

      - name: create release
        uses: actions/create-release@v1
        if: ${{ steps.changelog.outputs.skipped == 'false' }}
        env:
          GITHUB_TOKEN: ${{ secrets.CHANGELOG_RELEASE }}
        with:
          tag_name: ${{ steps.changelog.outputs.tag }}
          release_name: ${{ steps.changelog.outputs.tag }}
          body: ${{ steps.changelog.outputs.clean_changelog }}

But the downside to this is, this relies heavily on Commit message format to perform the releases and moving forward, commits should start with fix, feat,docs etc.... If we decide to go with this approach.

[danielledeleo]

goreleaser may be a good option as well! I believe it can also generate Homebrew recipes, if that is desired.

[IgnorantSapient]

goreleaser looks promising, should we commit to it?

[ignatk]

I'm a bit skeptical for third-party actions, but GitHub's create-release seems not maintained anymore. Is there something else we can do without relying on third-party actions?

[IgnorantSapient]

We can write our own go program that would achieve it. But what is your idea workflow? What would it look like?

[danielledeleo]

I'm a bit skeptical for third-party actions

Goreleaser can also be run manually (i.e. write your own Action to invoke it).

[ignatk]

I've implemented a rudimentary release asset upload in #52