On Wed, 7 Dec 2016 17:34:27 +0530
Mrudula Varimadugu wrote:
> Still not working.
> I tried by keeping die("Kaboom!\n"); in the pre-receive file.
> but still it pushed my commit, it didn't fail.
> see the output below when I tried individually ./pre-receive it
> printed Kaboom and it came out, but
Yeah I kept my hook in $Git_dir/hooks and made the file as executable
I have written code to check the latest commit message enforce with jira
ticket otherwise push should reject.
On Dec 7, 2016 6:27 PM, "Konstantin Khomoutov" <
flatw...@users.sourceforge.net> wrote:
On Wed, 7 Dec 2016 17:34:27 +
Hi
Still not working.
I tried by keeping die("Kaboom!\n"); in the pre-receive file.
but still it pushed my commit, it didn't fail.
see the output below when I tried individually ./pre-receive it printed
Kaboom and it came out, but when I try to push it didnt.
$ ./pre-receive
Kaboom!
mvari (GIT_DI
On Wed, 7 Dec 2016 02:58:22 -0800 (PST)
mrudula.varimad...@gmail.com wrote:
> I tried the below,
> when I am individually running ./pre-receive its working, but when I
> try to push even If am not giving jirs issue its pushing to remote.
> Please help me on this
Good to know you actually tried to
I tried the below,
when I am individually running ./pre-receive its working, but when I try to
push even If am not giving jirs issue its pushing to remote.
Please help me on this
#!/usr/bin/perl
# Force JIRA ticket in commit messages
my $errors = 0;
chomp(my @commits = `git rev-parse -
On Wed, 7 Dec 2016 02:27:12 -0800 (PST)
mrudula.varimad...@gmail.com wrote:
> I am looking for this code.
> Can you provide me the full script/code after doing this changes
No. I don't have any.
But what have you tried [1] before asking for it?
1. http://whathaveyoutried.com
> On Thursday, Se
Hi
I am looking for this code.
Can you provide me the full script/code after doing this changes
On Thursday, September 5, 2013 at 3:32:27 PM UTC+5:30, Konstantin Khomoutov
wrote:
>
> On Wed, 4 Sep 2013 11:39:21 -0700 (PDT)
> Ling > wrote:
>
> > Thanks Konstantin, Yes I tried git log $newname
On Wed, 4 Sep 2013 11:39:21 -0700 (PDT)
Ling wrote:
> Thanks Konstantin, Yes I tried git log $newname $(git merge-base
> $oldname $newname) and it works fine.
That is not quite correct a call -- the proper one is
git log $newname ^$basename
or, expanded,
git log $newname ^$(git merge-base $ol
Thanks Konstantin, Yes I tried git log $newname $(git merge-base $oldname
$newname) and it works fine.
Thanks
Ling
On Wednesday, September 4, 2013 10:55:41 AM UTC-4, Konstantin Khomoutov
wrote:
> On Wed, 4 Sep 2013 06:50:47 -0700 (PDT)
> Ling > wrote:
>
> > Thanks Konstantin and quesiton
On Wed, 4 Sep 2013 06:50:47 -0700 (PDT)
Ling wrote:
> Thanks Konstantin and quesiton? you mean git log $newname ^$basename,
> and is the $newname $basename are: newname is the after pushed
> refs/heads/Lingfei_test2? and basename is before pushed:
> refs/heads/Lingfei_test2?
No, $newname and $
On Wed, 4 Sep 2013 07:15:43 -0700 (PDT)
Ling wrote:
> I think what we want to have a hook that on the server repository to
> prevent the local pushes, so I think if we using git log on the
> server repo, this won't protect us
Why? Using a pre-receive hook to check what has been pushed is the
r
Hello Konstantin,
I think what we want to have a hook that on the server repository to
prevent the local pushes, so I think if we using git log on the server
repo, this won't protect us since git log is only created after local
pushes, right? and also since when our developers clone the repo t
Thanks Konstantin and quesiton? you mean git log $newname ^$basename, and
is the $newname $basename are: newname is the after pushed
refs/heads/Lingfei_test2? and basename is before pushed:
refs/heads/Lingfei_test2?
Thanks
Lingfei
On Wednesday, September 4, 2013 9:36:10 AM UTC-4, Konstantin
On Wed, 4 Sep 2013 16:59:14 +0400
Konstantin Khomoutov wrote:
[...]
> For each ref to be updated:
>
> 1) Call `git merge-base $oldname $newname` -- this will give you the
>name of a commit which is common between the old and the new state
> of the ref. In the simplest case -- a fast-forwar
On Wed, 4 Sep 2013 04:31:26 -0700 (PDT)
Ling wrote:
> Thanks Thomas, And yes I had read this and also I tried with git log
> but this won't works since git log is only created after the push,
> which means it won't compare the new push comment, it only compare
> the previous pushed comment to tri
15 matches
Mail list logo
