From 3fd5be4d1e7b2ae02fc5fb36f005d66c4c0ca769 Mon Sep 17 00:00:00 2001 From: Mike McQuaid Date: Tue, 5 Dec 2023 08:22:53 -0500 Subject: [PATCH] docs/Homebrew-homebrew-cask-Maintainer-Guide: remove rebase and merge button reference. --- docs/Homebrew-homebrew-cask-Maintainer-Guide.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/Homebrew-homebrew-cask-Maintainer-Guide.md b/docs/Homebrew-homebrew-cask-Maintainer-Guide.md index 8ebd7582a5c877..b53cb18854121d 100644 --- a/docs/Homebrew-homebrew-cask-Maintainer-Guide.md +++ b/docs/Homebrew-homebrew-cask-Maintainer-Guide.md @@ -26,8 +26,6 @@ Note that unlike formulae, casks do not consider the `sha256` stanza to be a mea In general, using GitHub's "Merge" button is the best way to merge a PR. This can be used when the PR modifies only one cask, regardless of the number of commits or whether the commit message format is correct. When merging using this method, the commit message can be modified if needed. Usually, version bump commit messages follow the form `CASK NEW_VERSION`. -If the PR modifies multiple casks, use the "Rebase and Merge" button to merge the PR. This will use the commit messages from the PR, so make sure that they are appropriate before merging. If needed, checkout the PR, squash/reword the commits and force-push back to the PR branch to ensure the proper commit format. - Finally, make sure to thank the contributor for submitting a PR! ## Other Tips