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

Add publishConfig.tag instructions to README ... #149

Merged
merged 1 commit into from
Feb 18, 2020

Conversation

pixelbandito
Copy link
Contributor

... tweak notes on yalc and casing of GitHub

1. Bump the `package.json`'s version _using [semver](https://semver.org/)_. We're currently in alpha, and probably will be for a while. Versions are cheap.
2. If all tests look good (`yarn test`), submit a pull-request against the master branch through Github. We're using the master branch for now, but by the time we're out of alpha, we'll have a dev branch.
1. In `package.json`, bump the `version` and `publishConfig.tag` properties _using [semver](https://semver.org/)_. `publishConfig.tag` should start with a "v", but otherwise be identical to `version`.
2. If all tests look good (`yarn test`), submit a pull-request against the master branch through GitHub.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd still like to see us have a more refined branching strategy, but I don't see any value in a dev branch yet since we build and deploy on every approved change.

We could start making a branch-per-version soon, if we start having enough changes per week to merit it.

@pixelbandito pixelbandito merged commit b893687 into master Feb 18, 2020
@pixelbandito pixelbandito deleted the readme-update-tag-version-tweak-yalc-notes branch February 18, 2020 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants