It adds semantic-release to elegantly handle new releases + CHANGELOG generation based on semantic versioning.
For everything to work as expected, an NPM_TOKEN must be set for this repo's actions.
Furthermore, let's discuss the package name 😉. I left the gpt-crawler as a suggestion as I think it's available on NPM (see https://www.npmjs.com/package/gpt-crawler) but I will leave this up to you 🤗.
🆘 There is a catch here, since the git commits must follow conventional commits (https://www.conventionalcommits.org/en/v1.0.0/) for the releases to be generated as expected, I would appreciate your thoughts and comments on strategies to standardise commits in this way (addressable either on this PR on another PR).
This PR is a follow up from:
38
What does this PR do?
It adds semantic-release to elegantly handle new releases + CHANGELOG generation based on semantic versioning.
For everything to work as expected, an
NPM_TOKEN
must be set for this repo's actions.Furthermore, let's discuss the package name 😉. I left the
gpt-crawler
as a suggestion as I think it's available on NPM (see https://www.npmjs.com/package/gpt-crawler) but I will leave this up to you 🤗.🆘 There is a catch here, since the git commits must follow conventional commits (https://www.conventionalcommits.org/en/v1.0.0/) for the releases to be generated as expected, I would appreciate your thoughts and comments on strategies to standardise commits in this way (addressable either on this PR on another PR).
Related