From: Ted Zlatanov <tzz@lifelogs.com>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Toon Claes <toon@iotcl.com>, emacs-devel@gnu.org
Subject: Re: EMBA (Emacs Gitlab CI build server) is now *public* available
Date: Wed, 30 Jan 2019 20:39:44 +0000 [thread overview]
Message-ID: <4l9pc227.fsf@lifelogs.com> (raw)
In-Reply-To: <87zhril4wz.fsf@gmx.de> (Michael Albinus's message of "Wed, 30 Jan 2019 13:13:16 +0100")
On Wed, 30 Jan 2019 13:13:16 +0100 Michael Albinus <michael.albinus@gmx.de> wrote:
MA> Toon Claes <toon@iotcl.com> writes:
>>> Don't know. Likely not, because it reflects the git clone on the emba
>>> server itself, which is triggered with Ted's credentials.
>>
>> Yes. I suggest we create a "bot" user that pushes the changes. This
>> should reduce the confusion.
MA> Good idea. This shows also clearly the difference, when somebody has
MA> started a pipeline manually.
I think it's correct to show the pushing user, because the push is what
triggered the pipeline and could have contained multiple commits by
multiple authors. So a bot user makes a lot of sense for our current
setup, pure mirroring.
...and I see Toon already implemented it :) Thank you Toon!!
Ted
next prev parent reply other threads:[~2019-01-30 20:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 16:29 EMBA (Emacs Gitlab CI build server) is now available Ted Zlatanov
2018-12-31 17:54 ` Michael Albinus
2018-12-31 18:05 ` Ted Zlatanov
2019-01-01 12:08 ` Michael Albinus
2019-01-01 14:56 ` Ted Zlatanov
2019-01-01 16:51 ` Michael Albinus
2019-01-02 15:05 ` Justin Joseph Kaipada
2019-01-02 15:17 ` Michael Albinus
2019-01-04 11:52 ` Michael Albinus
2019-01-05 8:01 ` Toon Claes
2019-01-30 8:53 ` EMBA (Emacs Gitlab CI build server) is now *public* available Toon Claes
2019-01-30 9:46 ` Robert Pluim
2019-01-30 10:00 ` Michael Albinus
2019-01-30 11:23 ` Toon Claes
2019-01-30 12:13 ` Michael Albinus
2019-01-30 20:39 ` Ted Zlatanov [this message]
2019-02-05 12:50 ` Robert Pluim
2019-02-05 12:55 ` Michael Albinus
2019-02-05 14:58 ` Robert Pluim
2019-02-05 15:42 ` Ted Zlatanov
2019-02-05 15:50 ` Robert Pluim
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4l9pc227.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
--cc=toon@iotcl.com \
/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/emacs.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).