lekterable/branchlint-action

Lint your git branch names using github action.

branchlint-action's Issues

Error: Cannot read property 'head' of undefined

Workflow file: https://github.com/oneleif/Discord-Bot/actions/runs/3011571486/workflow
Workflow failure: https://github.com/oneleif/Discord-Bot/actions/runs/3011571486

Previous workflow success: https://github.com/oneleif/Discord-Bot/actions/runs/3011541759

Incorporate major release tags

It would be really useful to have major release tags like some of the other major public github actions. Like, for that PR I submitted, it was not a breaking change. So, the semantic version was correctly incremented by a minor (2.1.0). And the major version, v2, stayed the same. But I had to go update all my repositories that used lekterable/branchlint-action. It would be helpful to downstream users to be able to reference the major version tag in their workflow files.

I would just like to write uses: lekterable/branchlint-action@v2

For example:
https://github.com/actions/checkout/tags

please update for node.js 20

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: lekterable/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Feature Request: Update actions to use Node.js 16

Hey @lekterable, thanks for a great tool! Is there any chance to update the action to use Node.js 16? The older node version is being deprecated this year, all your users right now receiving a warning like this:

Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: lekterable/[email protected]. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Thanks again in any case!