You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, firehose publishing generally publishes from the head commit. This generally happens thuswise:
firehose writes a publishing comment into a PR
that PR eventually lands
a contributor with commit access clicks on the 'publish' link in the PR; that opens a pre-populated release page that (when created) will trigger publishing
If there are many packages in a repo, we don't always want to publish from the latest commit; other commits may have landed after the original PR. When creating the release page info, we should add some text to encourage the user to tag a specific commit (which will frequently, but not always, be head). The commit to tag add can be selected from the 'target', 'recent commits' dropdown:
The text was updated successfully, but these errors were encountered:
Currently, firehose publishing generally publishes from the head commit. This generally happens thuswise:
If there are many packages in a repo, we don't always want to publish from the latest commit; other commits may have landed after the original PR. When creating the release page info, we should add some text to encourage the user to tag a specific commit (which will frequently, but not always, be head). The commit to tag add can be selected from the 'target', 'recent commits' dropdown:
The text was updated successfully, but these errors were encountered: