chore: add release PR flow #245
Conversation
erezrokah
added
the
type: chore
| 1. Merge the release PR | ||
| 2. Switch to the default branch `git checkout master` | ||
| 3. Pull latest changes `git pull` | ||
| 4. Publish the package `npm publish` |
There was a problem hiding this comment.
At some point, we might want to have a common CONTRIBUTING.md to avoid duplication between repositories, what do you think?
At least for part of it.
There was a problem hiding this comment.
I agree, I forgot to do it in node-template. See netlify/node-template#13
There was a problem hiding this comment.
I am also thinking of just putting some URL to point a common file, so we don't need to update all CONTRIBUTING.md when we make changes, what do you think?
There was a problem hiding this comment.
We could create a dedicate repo just for code of conduct and contributing guide or put it under https://github.com/netlify/eslint-config-node, WDYT?
There was a problem hiding this comment.
Either works! 👍
Maybe eslint-config-node would make some sense for the contributing guide since linting and code formatting are a big part of the flow. But a separate repository would work as well.
erezrokah
force-pushed
the
chore/add_release_please
branch
from
1b9158e to
b9f2008
Compare
Fixes #243
We should merge #244 first, then publish a release, then merge this PR.