Skip to content

Conversation

@github-learning-lab
Copy link
Contributor

Step 13: Approve the backport pull request

If you have previous release branches that are impacted by this bug, you might need to make a few retroactive pull requests. Generally, we do this by using git cherry-pick to apply just those commits that should be backported.

In our case, no new changes have been merged into main since we shipped our hotfix, so we can merge the entire branch as is.

⌨️ Activity: Backport the hotfix to release v1.0

  1. Approve this pull request

I'll respond below after you approve

githubteacher and others added 2 commits November 5, 2018 22:14
Co-authored-by: github-learning-lab[bot] <37936606+github-learning-lab[bot]@users.noreply.github.com>
@github-learning-lab github-learning-lab bot mentioned this pull request Dec 1, 2020
@github-learning-lab github-learning-lab bot merged commit bd3c749 into release-v1.0 Dec 1, 2020
@github-learning-lab
Copy link
Contributor Author

Congratulations! Your hotfix is now:

  • on the main branch (for any new code)
  • on the release branch (so we can cut release v1.0.1)

Go to the next issue to continue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants