Add script to release to git tags #486
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hedgepigdaniel
force-pushed
the
feat/git-release
branch
from
1cbe063
to
865d426
Compare
theKashey
reviewed
Dec 20, 2019
theKashey
reviewed
Jan 3, 2020
CONTRIBUTING.md
Outdated
|
|
||
| You can use `yarn run release-from-git` to create releases as tags on github. This requires that: | ||
| - Your git remote (where you want to publish the tags) is `origin` | ||
| - Your commit messages follow the conventional commits specification |
There was a problem hiding this comment.
this is not quite clear. A minimal example would help a lot.
There was a problem hiding this comment.
I added a minimal example and a link to the spec
hedgepigdaniel
force-pushed
the
feat/git-release
branch
from
5cb30bf
to
cb2fab8
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When making a private fork to develop a change, it is difficult to test the change with another project.
yarn linkworks but requires extra steps each time the project is checked out. Installing from git doesn't work easily because the build assets are not in the repository and because the repository is a monorepo.This adds a script modelled after respond-framework/rudy#34 which makes a git tag containing the built version of each package that has changed since the last release (as it would be published to NPM).
My fork of
npm-publish-gitis used because of ysoftwareab/npm-publish-git#4Test plan
I created an example release containing the changes from #483: