Run deploys to npm whenever a new tag is pushed to a stable branch#19742
Run deploys to npm whenever a new tag is pushed to a stable branch#19742hramos wants to merge 2 commits intofacebook:masterfrom
Conversation
|
@hramos I tried to find reviewers for this pull request and wanted to ping them to take another look. However, based on the blame information for the files in this pull request I couldn't find any reviewers. This sometimes happens when the files in the pull request are new or don't exist on master anymore. Is this pull request still relevant? If yes could you please rebase? In case you know who has context on this code feel free to mention them in a comment (one person is fine). Thanks for reading and hope you will continue contributing to the project. |
|
Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours has expired. Before we can review or merge your code, we need you to email cla@fb.com with your details so we can update your status. |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
facebook-github-bot
left a comment
There was a problem hiding this comment.
hramos is landing this pull request. If you are a Facebook employee, you can view this diff on Phabricator.
|
This pull request was closed by @hramos in 0541c7b. Once this commit is added to a release, you will see the corresponding version tag below the description at 0541c7b. If the commit has a single |
This has been tested in
0.56-stableand was used to deploy the0.56.0-rc.2release.