mscwilson/changelog-creator

Auto changelog

changelog-creator's Issues

Start again from scratch

Link Action with Ruby script

To use the Github API

Create fancy LOG

the kind of changelog for release notes. Commits in categories. Note breaking changes. Also external contributors probably.
e.g.

New features
Add an amazing new feature (#1) BREAKING CHANGE
Track a new kind of event (#4) - thanks @mscwilson! BREAKING CHANGE
Output winning lottery numbers (#6)

Bug fixes
Fix events being randomly deleted (#8)

Under the hood
Remove secret keys (#5)

Update version as well as CHANGELOG

Will need a file describing where in the codebase the version is - uses an Input
More difficult is then commiting multiple files. Lots of refactoring probably needed.

Provide a different base branch

in case not main/master

Do something about tag triggers

Find out how to commit multiple files

six issues

Try some stuff

Add output

Add abstraction

Add some tests

Script works, need more unit tests. Don't worry about integration tests with real API calls for now.

five

Fix update_file not working if no existing file

Test issue

Another test issue

Provide version file

Add workflows

run this action, in this repo!

Update README

Specify the desired operation with inputs

Action inputs so it would be used like

      - name: Run ruby script
        id: release-notes
        uses: mscwilson/[email protected]
        env:
          ACCESS_TOKEN: ${{ secrets.GITHUB_TOKEN }}
        with:
          operation: "github release notes"

Generate Changelog via Dockerfile

issue three

Get external contributors more accurately

Not having a Snowplow email address isn't the best determinant. Greg is not an external contributor.

Check to see if the action already ran

There was some problem when I tested it last for CHLOG creation. There was a merge conflict and for some reason no PR opened event occurred. So the action didn't run, because I'd specified to only run for pull_request && "opened".

Allow it to run whenever and not break.

Use logic correctly

another one

first issue

hello this is a filler issue

Generate changelog using GH action

the seventh issue

Fix logic for the release notes commits

Currently is hacky. Make not hacky.

Rename "Miscellaneous" category to "Changes"

Turn and face the strange

octo issue

Set up Octokit

issue four

tenth issue

Loosen tag requirements

So "enhancement" or "feature" works instead of only "type:enhancement"

Add a CI workflow

nine