Skip to content
This repository was archived by the owner on Apr 10, 2026. It is now read-only.
This repository was archived by the owner on Apr 10, 2026. It is now read-only.

Create a bot or process for creating releases and verifying commit guidelines #102

Description

@alewitt2

used these resources as examples.. may need to rewrite ourselves to not steal their work.
https://eslint.org/docs/developer-guide/contributing/pull-requests#step-2-make-your-changes
https://github.com/eslint/eslint-github-bot/blob/master/docs/commit-message-check.md
https://github.com/eslint/eslint-github-bot
https://github.com/probot/probot

useful command for generating release descriptions

git checkout master
git pull origin
export NUM_COMMITS=5
git log --pretty=format:"[\`%h\`](https://github.com/razee-io/$(basename $(git rev-parse --show-toplevel))/commit/%H) %s" -"${NUM_COMMITS}"

or a one line option to get the pretty print between HEAD and the latest release

git log --pretty=format:"[\`%h\`](https://github.com/razee-io/$(basename $(git rev-parse --show-toplevel))/commit/%H) %s" HEAD..."$(curl --silent https://api.github.com/repos/razee-io/$(basename $(git rev-parse --show-toplevel))/releases/latest | jq -r .target_commitish)" | pbcopy

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions