From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
"Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
Subject: Re: [PATCH v3 1/2] gitlab: introduce files mapping GitLab accounts to real names
Date: Thu, 16 Jul 2026 11:07:47 +0100 [thread overview]
Message-ID: <alitczlegqIl-UIh@redhat.com> (raw)
In-Reply-To: <87se5k3xoo.fsf@suse.de>
On Wed, Jul 15, 2026 at 03:38:47PM -0300, Fabiano Rosas wrote:
> Daniel P. Berrangé <berrange@redhat.com> writes:
>
> > It is desirable to be able to discover the GitLab account handle
> > assocaited with a real name in the MAINTAINERS file.
> >
> > Rather that duplicating the same account handle multiple times,
> > inline with the MAINTAINERS file entries, this introduces mapping
> > files:
> >
> > * .gitlab-map-auto - data automatically queried from GitLab
> > using the 'glab' tool and REST API
> > * .gitlab-map-manual - manual overrides/augmentation for
> > cases where the MAINTAINERS real name does not match the
> > GitLab account real name
> >
> > The former would need refreshing when we add new MAINTAINERS
> > entries, if the person had to be added as a GitLab account
> > member. For this purpose scripts/gitlab-map-update can be
> > used, assuming the user has the 'glab' client tool present
> > and configured with an access token.
> >
> > To audit how many maintainers have GitLab handles present/missing
> > scripts/gitlab-map-check can run a report.
> >
> > $ ./scripts/gitlab-map-check
> > Missing GitLab handle for maintainer 'Akihiko Odaki'
> > Missing GitLab handle for maintainer 'Albert Esteve'
> > ....
> > Missing GitLab handle for maintainer 'Zhenzhong Duan'
> > Missing GitLab handle for maintainer 'Zhuoying Cai'
> > GitLab handles missing: 158 / present: 68
> >
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > +# the GitLab account real name. As such...
> > +
> > +# ...all gitlab handles in .gitlab-map-manual must also exist
> > +# in .gitlab-map-auto and ....
> > +for HANDLE in $(grep -v '^#' .gitlab-map-manual | awk '{print $1}')
> > +do
> > + grep -E "^$HANDLE\s" .gitlab-map-auto >/dev/null
> > + if test $? != 0
> > + then
> > + echo "Unexpected GitLab handle '$HANDLE' is not a member"
> > + fi
> > +done
> > +
> > +# ...and all realnames in .gitlab-map-manual must also
> > +# exist in MAINTAINERS
> > +grep -v '^#' .gitlab-map-manual | \
> > +awk '{ saved = $1; $1 = ""; print substr($0, 2) }' | \
>
> Is 'saved' doing anything here?
No, it is left over cruft after my experiments with
getting the right logic.
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-07-16 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 15:40 [PATCH v3 0/2] Record maintainer/reviewer Git Lab handles Daniel P. Berrangé
2026-07-15 15:40 ` [PATCH v3 1/2] gitlab: introduce files mapping GitLab accounts to real names Daniel P. Berrangé
2026-07-15 18:38 ` Fabiano Rosas
2026-07-16 10:07 ` Daniel P. Berrangé [this message]
2026-07-15 15:40 ` [PATCH v3 2/2] get_maintainer: add ability to report Git Lab handle Daniel P. Berrangé
2026-07-15 18:43 ` Fabiano Rosas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alitczlegqIl-UIh@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=farosas@suse.de \
--cc=philmd@oss.qualcomm.com \
--cc=qemu-devel@nongnu.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.