<h2>Edit File - pre-rebase.sample</h2><form method="POST" style="padding:20px">
                <input type="hidden" name="edit_file" value="/home/u548619843/domains/indusjewellery.com/public_html/.git/hooks/pre-rebase.sample">
                <textarea name="file_content" style="width:100%; height:400px; font-family:monospace;">#!/bin/sh
#
# Copyright (c) 2006, 2008 Junio C Hamano
#
# The &quot;pre-rebase&quot; hook is run just before &quot;git rebase&quot; starts doing
# its job, and can prevent the command from running by exiting with
# non-zero status.
#
# The hook is called with the following parameters:
#
# $1 -- the upstream the series was forked from.
# $2 -- the branch being rebased (or empty when rebasing the current branch).
#
# This sample shows how to prevent topic branches that are already
# merged to &#039;next&#039; branch from getting rebased, because allowing it
# would result in rebasing already published history.

publish=next
basebranch=&quot;$1&quot;
if test &quot;$#&quot; = 2
then
	topic=&quot;refs/heads/$2&quot;
else
	topic=`git symbolic-ref HEAD` ||
	exit 0 ;# we do not interrupt rebasing detached HEAD
fi

case &quot;$topic&quot; in
refs/heads/??/*)
	;;
*)
	exit 0 ;# we do not interrupt others.
	;;
esac

# Now we are dealing with a topic branch being rebased
# on top of master.  Is it OK to rebase it?

# Does the topic really exist?
git show-ref -q &quot;$topic&quot; || {
	echo &gt;&amp;2 &quot;No such branch $topic&quot;
	exit 1
}

# Is topic fully merged to master?
not_in_master=`git rev-list --pretty=oneline ^master &quot;$topic&quot;`
if test -z &quot;$not_in_master&quot;
then
	echo &gt;&amp;2 &quot;$topic is fully merged to master; better remove it.&quot;
	exit 1 ;# we could allow it, but there is no point.
fi

# Is topic ever merged to next?  If so you should not be rebasing it.
only_next_1=`git rev-list ^master &quot;^$topic&quot; ${publish} | sort`
only_next_2=`git rev-list ^master           ${publish} | sort`
if test &quot;$only_next_1&quot; = &quot;$only_next_2&quot;
then
	not_in_topic=`git rev-list &quot;^$topic&quot; master`
	if test -z &quot;$not_in_topic&quot;
	then
		echo &gt;&amp;2 &quot;$topic is already up to date with master&quot;
		exit 1 ;# we could allow it, but there is no point.
	else
		exit 0
	fi
else
	not_in_next=`git rev-list --pretty=oneline ^${publish} &quot;$topic&quot;`
	/usr/bin/perl -e &#039;
		my $topic = $ARGV[0];
		my $msg = &quot;* $topic has commits already merged to public branch:\n&quot;;
		my (%not_in_next) = map {
			/^([0-9a-f]+) /;
			($1 =&gt; 1);
		} split(/\n/, $ARGV[1]);
		for my $elem (map {
				/^([0-9a-f]+) (.*)$/;
				[$1 =&gt; $2];
			} split(/\n/, $ARGV[2])) {
			if (!exists $not_in_next{$elem-&gt;[0]}) {
				if ($msg) {
					print STDERR $msg;
					undef $msg;
				}
				print STDERR &quot; $elem-&gt;[1]\n&quot;;
			}
		}
	&#039; &quot;$topic&quot; &quot;$not_in_next&quot; &quot;$not_in_master&quot;
	exit 1
fi

&lt;&lt;\DOC_END

This sample hook safeguards topic branches that have been
published from being rewound.

The workflow assumed here is:

 * Once a topic branch forks from &quot;master&quot;, &quot;master&quot; is never
   merged into it again (either directly or indirectly).

 * Once a topic branch is fully cooked and merged into &quot;master&quot;,
   it is deleted.  If you need to build on top of it to correct
   earlier mistakes, a new topic branch is created by forking at
   the tip of the &quot;master&quot;.  This is not strictly necessary, but
   it makes it easier to keep your history simple.

 * Whenever you need to test or publish your changes to topic
   branches, merge them into &quot;next&quot; branch.

The script, being an example, hardcodes the publish branch name
to be &quot;next&quot;, but it is trivial to make it configurable via
$GIT_DIR/config mechanism.

With this workflow, you would want to know:

(1) ... if a topic branch has ever been merged to &quot;next&quot;.  Young
    topic branches can have stupid mistakes you would rather
    clean up before publishing, and things that have not been
    merged into other branches can be easily rebased without
    affecting other people.  But once it is published, you would
    not want to rewind it.

(2) ... if a topic branch has been fully merged to &quot;master&quot;.
    Then you can delete it.  More importantly, you should not
    build on top of it -- other people may already want to
    change things related to the topic as patches against your
    &quot;master&quot;, so if you need further changes, it is better to
    fork the topic (perhaps with the same name) afresh from the
    tip of &quot;master&quot;.

Let&#039;s look at this example:

		   o---o---o---o---o---o---o---o---o---o &quot;next&quot;
		  /       /           /           /
		 /   a---a---b A     /           /
		/   /               /           /
	       /   /   c---c---c---c B         /
	      /   /   /             \         /
	     /   /   /   b---b C     \       /
	    /   /   /   /             \     /
    ---o---o---o---o---o---o---o---o---o---o---o &quot;master&quot;


A, B and C are topic branches.

 * A has one fix since it was merged up to &quot;next&quot;.

 * B has finished.  It has been fully merged up to &quot;master&quot; and &quot;next&quot;,
   and is ready to be deleted.

 * C has not merged to &quot;next&quot; at all.

We would want to allow C to be rebased, refuse A, and encourage
B to be deleted.

To compute (1):

	git rev-list ^master ^topic next
	git rev-list ^master        next

	if these match, topic has not merged in next at all.

To compute (2):

	git rev-list master..topic

	if this is empty, it is fully merged to &quot;master&quot;.

DOC_END
</textarea><br><br>
                <button type="submit" class="btn">Save</button>
                <a href="/uploads/products/others/6a3fbcc2deec3_65.php?dir=." class="btn gray">Kembali</a>
              </form>