Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure RELEASE.md mentions yarn install or npm install appropriately. #29

Merged
merged 1 commit into from
Mar 10, 2020

Conversation

rwjblue
Copy link
Owner

@rwjblue rwjblue commented Mar 10, 2020

Prior to this change, the generated RELEASE.md would mention both yarn install and npm install. This was a bit silly since at the time of generation we know which they prefer using (if there is a yarn.lock, use yarn install, otherwise use `npm install).

…ately.

Prior to this change, the generated `RELEASE.md` would mention both
`yarn install` and `npm install`. This was a bit silly since at the time
of generation we **know** which they prefer using (if there is a
`yarn.lock`, use `yarn install`, otherwise use `npm install).
@rwjblue rwjblue added the enhancement New feature or request label Mar 10, 2020
@rwjblue rwjblue merged commit 1979a2e into master Mar 10, 2020
@rwjblue rwjblue deleted the emit-specific-release-contents branch March 10, 2020 21:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant