[QE-developers] R: R: Gitlab merge request

Pietro Davide Delugas pdelugas at sissa.it
Mon Aug 8 09:49:06 CEST 2022


Dear Laurent

all the interaction will go through comments and threads with the merge request session.
Just check the merge request page from time to time ( or, if you wish, subscribe for mail notifications).

B.T.W. I was just looking now and the M.R. has not appeared yet. It could be GitLab that is slow to update, but could you check again ?

for any issue with gitlab maybe it's easier to mail me directly ( pdelugas at sissa.it).

Pietro
________________________________
Da: developers <developers-bounces at lists.quantum-espresso.org> per conto di Laurent Pizzagalli <laurent.pizzagalli at univ-poitiers.fr>
Inviato: lunedì 8 agosto 2022 09:31
A: developers at lists.quantum-espresso.org <developers at lists.quantum-espresso.org>
Oggetto: Re: [QE-developers] R: Gitlab merge request

Dear Pietro,

thank you for your email and your help. Then it seems that I got it right for my merge request.
Can you please tell me if there is anything else I should do (or just wait for the merge request to be examined) ?
How will I know when the merge request has been processed?

Best regards

Laurent



Hello Laurent

it's not necessary to use shared runners to participate in the development of QE.
 It would be useful, but it has already happened that we were unable to read pipelines that were running on other forks.

we usually don't provide names for assignees or reviewers.
You can do that,  but as people may be busy, it may be better if you first check offline with
the people you want to involve.

best regards
Pietro

________________________________
Da: developers <developers-bounces at lists.quantum-espresso.org<https://lists.quantum-espresso.org/mailman/listinfo/developers>> per conto di Laurent Pizzagalli <laurent.pizzagalli at univ-poitiers.fr<https://lists.quantum-espresso.org/mailman/listinfo/developers>>
Inviato: martedì 2 agosto 2022 11:51
A: developers at lists.quantum-espresso.org<https://lists.quantum-espresso.org/mailman/listinfo/developers> <developers at lists.quantum-espresso.org<https://lists.quantum-espresso.org/mailman/listinfo/developers>>
Oggetto: [QE-developers] Gitlab merge request

Dear colleagues,

I made a few additions to quantum espresso, according to the procedure
described in the Developer's manual (i.e. making a fork of the develop
version on GitLab, cloning this fork locally, and working on a new branch).
I push my changes to gitlab and next created a merge request for my branch.
However, in both cases, I got messages from gitlab telling me that I
should validate my account to use 'shared runners'?

I am not an expert of git, and even less of gitlab, then I am a bit
unsure of the status of my merge request.
My questions are :
- Is it really needed to use 'shared runners' to participate in the
development of QE ?
- Should I provide specific names for assignee and reviewer in the merge
request ?

Thank you

Best regards

Laurent


--
                                                       ,,,     __,
                                                      /'^'\   |__|
                                                     ( o o )  |
--------------------------------------------------oOOO--(_)--OO|o------
<Laurent.Pizzagalli at univ-poitiers.fr><mailto:Laurent.Pizzagalli at univ-poitiers.fr>
http://laurent.pizzagalli.free.fr/            Tel +33 549 49 74 99
------------------------------------------    Fax +33 549 49 66 92
Institut P'
Departement de Physique et de Mécanique des Matériaux
CNRS UPR 3346
Université de Poitiers
SP2MI
TSA 41123                                          .oooO
86073 Poitiers Cedex 9, FRANCE                     (   )   Oooo.
----------------------------------------------------\ (----(   )-------
                                                     \_)    ) /
                                                           (_/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quantum-espresso.org/pipermail/developers/attachments/20220808/2fe2abe6/attachment-0001.html>


More information about the developers mailing list