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
{{ message }}
This repository has been archived by the owner on Feb 19, 2023. It is now read-only.
When I merge a pull request with @jekyllbot: merge +bug it would be cool if, in addition to merging into master@jekyllbot could cherry-pick the merge commit into the appropriate *-stable branch and update History.markdown in that branch. That way, I would never have to deal with manually backporting, but could just cut a release from that branch and trust that it has all the latest bug fixes already.
The text was updated successfully, but these errors were encountered:
This is very much wishful thinking
When I merge a pull request with
@jekyllbot: merge +bug
it would be cool if, in addition to merging intomaster
@jekyllbot could cherry-pick the merge commit into the appropriate*-stable
branch and updateHistory.markdown
in that branch. That way, I would never have to deal with manually backporting, but could just cut a release from that branch and trust that it has all the latest bug fixes already.The text was updated successfully, but these errors were encountered: