From: "Ludovic Courtès" <ludo@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Updating the “pre-push” Git hook
Date: Mon, 25 May 2020 23:31:19 +0200 [thread overview]
Message-ID: <87lflfsnvc.fsf@gnu.org> (raw)
In-Reply-To: <20200525055055.GA17182@E5400> (Efraim Flashner's message of "Mon, 25 May 2020 08:50:55 +0300")
Efraim Flashner <efraim@flashner.co.il> skribis:
> I'd probably run 'guix environment guix -- git push origin master' and
> view it as an additional safe guard to not push to the wrong branch or
> something, similar to how I view the password on the key. I bet there's
> an option to create a repo-specific alias in .git/config so that 'git
> push' will run inside 'guix environment guix'.
OK.
> I'm not convinced that my case is unique or that it should hold back the
> change. How does it work if 'make authenticate' fails?
‘git push’ fails, just like with the current pre-push hook.
Ludo’.
next prev parent reply other threads:[~2020-05-25 21:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 20:44 Updating the “pre-push” Git hook Ludovic Courtès
2020-05-22 21:17 ` Leo Famulari
2020-05-24 7:27 ` Ricardo Wurmus
2020-05-24 21:44 ` Ludovic Courtès
2020-05-25 9:50 ` Ricardo Wurmus
2020-05-25 22:04 ` Ludovic Courtès
2020-05-24 6:41 ` Efraim Flashner
2020-05-24 21:45 ` Ludovic Courtès
2020-05-25 5:50 ` Efraim Flashner
2020-05-25 21:31 ` Ludovic Courtès [this message]
2020-05-25 20:13 ` Vagrant Cascadian
2020-05-25 21:37 ` Ludovic Courtès
2020-05-26 16:41 ` Leo Famulari
2020-05-29 16:45 ` Heads-up: “pre-push” Git hook updated Ludovic Courtès
2020-05-29 17:07 ` Pierre Neidhardt
2020-05-29 18:39 ` Christopher Baines
2020-06-04 11:50 ` Ludovic Courtès
2020-06-04 18:33 ` Christopher Baines
2020-06-08 18:41 ` Vagrant Cascadian
2020-06-09 15:46 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lflfsnvc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).