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 script to release to git tags #486

Merged
merged 3 commits into from
Jan 9, 2020

Conversation

hedgepigdaniel
Copy link
Contributor

Summary

When making a private fork to develop a change, it is difficult to test the change with another project. yarn link works 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-git is used because of ysoftwareab/npm-publish-git#4

Test plan

I created an example release containing the changes from #483:

package.json Outdated Show resolved Hide resolved
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
Copy link
Collaborator

Choose a reason for hiding this comment

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

this is not quite clear. A minimal example would help a lot.

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 added a minimal example and a link to the spec

@gregberge gregberge merged commit 85074eb into gregberge:master Jan 9, 2020
@hedgepigdaniel hedgepigdaniel deleted the feat/git-release branch January 16, 2020 07:03
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.

None yet

3 participants