[gmx-developers] creating a branch of the gitlab repo

Christopher Mirabzadeh camirabzadeh at gmail.com
Mon Jan 4 00:23:13 CET 2021


Thank you, Pascal. I have opened an issue:
https://gitlab.com/gromacs/gromacs/-/issues/3861

The feature is up for discussion and I would also like access to the repo
in order to submit merge requests. As I get reacquainted with the code base
I would like to contribute where possible. I requested access through the
gitlab interface and my user id is
@camirabzadeh.

Cheers,

-ChrisM

On Sun, Jan 3, 2021 at 2:11 PM Pascal Merz <Pascal.Merz at colorado.edu> wrote:

> Hello Christopher,
>
> It’s best if you create a branch, there’s some problems running the CI for
> merge requests from forks. Please reply here if you find that you lack the
> required permissions, someone from the core team in Stockholm will be able
> to grant them to you.
>
> The latest stable release is 2020, which is branch release-2020 and has
> tags for minor releases. 2021 is currently a release candidate, on branch
> release-2021 with several tags for the beta and RC releases. For new
> features, you’ll want to target the next major release, however, so I’d
> strongly suggest you branch off of the current master.
>
> I’d also encourage you to open an issue on Gitlab explaining your planned
> feature and allowing for a discussion on how to best implement and later
> maintain it. The developer resources (and hence also the review resources)
> are limited, so having some design discussion ahead of time will save
> everyone time and potential frustration later on.
>
> Best,
> Pascal
>
>
> > On Jan 2, 2021, at 6:27 PM, Christopher Mirabzadeh <
> camirabzadeh at gmail.com> wrote:
> >
> > Hello all,
> >
> > I have a feature that I would like to add in a future release, of course
> only if I am able to create tests and follow proper style recs. Do I create
> a branch or just fork the gitlab repo? And then, is master the current
> release or is the current release under a different branch/tag?
> >
> > Thanks,
> >
> > -ChrisM
> > --
> > Gromacs Developers mailing list
> >
> > * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
> >
> > * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> >
> > * For (un)subscribe requests visit
> > https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
>
> --
> Gromacs Developers mailing list
>
> * Please search the archive at
> http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before
> posting!
>
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
>
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers
> or send a mail to gmx-developers-request at gromacs.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.sys.kth.se/pipermail/gromacs.org_gmx-developers/attachments/20210103/07015feb/attachment.html>


More information about the gromacs.org_gmx-developers mailing list