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
// ship.js.config
{
commentOnGitHubAfterRelease: true, // this name is totally temporary
}
With commentOnGitHubAfterRelease: true, at the end of yarn release:trigger, Ship.js will go to all the related PRs and leave comments like This PR is included in the recent release vx.y.z.
User could provide a config like the following to allow many use-cases.
// ship.config.jsconstcoreTeam=['username1','username2', ...];exportdefault{commentAfterRelease: ({
id,// issue or pr number,
type,// 'issue' | 'pull-request',
author,// username of the issue or pr})=>{returncoreMaintainers.indexOf(author)===-1;// notify only if it's coming from community}}// orexportdefault{commentAfterRelease: async({ id })=>{constlabels=awaitgetLabelsFromGitHub(id);returnlabels.indexOf("notify after release")>=0;}}
With
commentOnGitHubAfterRelease: true
, at the end ofyarn release:trigger
, Ship.js will go to all the related PRs and leave comments likeThis PR is included in the recent release vx.y.z
.It seems semantic-release does this, too.
example: downshift-js/downshift#971 (comment)
The text was updated successfully, but these errors were encountered: