Re: git rebase -- a suggestion
- From
Nanako Shiraishi <nanako3@lavabit.com>
- Date
- Oct 5, 2008, 13:26 UTC
- Message-ID
- <20081005222654.6117@nanako3.lavabit.com>
- In-Reply-To
- <b19eae4e0810021710v14a3901an1f793de00c439ba1@mail.gmail.com>
Documentation/git-rebase.txt talks about pre-rebase hook, but it appears that Documentation/git-hooks.txt does not have corresponding entry for it.
Signed-off-by: Nanako Shiraishi <nanako3@lavabit.com> --- "Robin Burchell" <w00t@inspircd.org> writes:
> would it perhaps be an idea to have a way to mark a tree 'public', and > disallow rebase *unless* --force was passed, or it was a public tree?
Documentation/githooks.txt | 7 +++++++ 1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/Documentation/githooks.txt b/Documentation/githooks.txt index 046a2a7..567ec03 100644 --- a/Documentation/githooks.txt +++ b/Documentation/githooks.txt @@ -130,6 +130,13 @@ parameter, and is invoked after a commit is made. This hook is meant primarily for notification, and cannot affect the outcome of 'git-commit'. +pre-rebase +---------- + +This hook is called by 'git-rebase' and can be used to prevent a branch +from getting rebased. + + post-checkout -----------
-- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/