Closed btmills closed 1 year ago
By the way, we could also tweet out the release, as I do in my repos: https://github.com/humanwhocodes/async-event-emitter/blob/e63c3b054c2fcdf422fc2f75ff1053801589d7f7/.github/workflows/release-please.yml#L33-L39
We already have our Twitter credentials as secrets to tweet out RFC updates, and at least so far, these automated tweets are still going out.
NPM_TOKEN
to the organization level and gave generator-eslint
access.
This configures the release-please action for
generator-eslint
. As we merge changes using Conventional Commits formatting, release-please will create and update a pending release PR. That PR will contain a changelog of any commits merged since the prior release. When we're ready to do the release, we'll merge that PR, and the workflow in this PR will update the changelog and publish the release to GitHub and npm.Separate from the code in this PR, I had to take a few manual steps:
release-please $package-name
release-please
."Only select packages and scopes" > select the package that we're setting up."All packages".new repository secretnew organization secret namedNPM_TOKEN
, and give access to the desired repository. If the token already exists, edit it to include access for the desired repository.