-
Notifications
You must be signed in to change notification settings - Fork 257
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
[js-repo-migration] Push Lerna git
tags from apollo-server
to this repo.
#140
Comments
git
tags from apollo-server
to this repo.git
tags from apollo-server
to this repo.
Merged
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Follow up to: #134, assuming it lands! (Currently approved, so signs point to yes).
This is to track the work of bringing the Git tags created during the Lerna publishing process of the JavaScript federation/gateway packages which are moving into this repository.
Those tags, once pushed (I have them staged locally, but you can't do a PR for Git tags), will take on the form of
@apollo/[email protected]
and@apollo/[email protected]
, much like the form they were in before on theapollo-server
repository. They will point to the correspondign commits based on the outcome produced by #134.The benefit to bringing them here is not only to allow Lerna to know where it left off (since it uses these tags to determine what has changed since the last relese), but also to simplify the process of
git
-ergonomics which allow us to see what has changed and when (in the past) without needing to consult the older repository (mostly because that isn't intuiative; even if it is technically where they were published from the tags will still capture precisely what was published to npm so having them in a single place is nice).The text was updated successfully, but these errors were encountered: