|
Hi Ferdie,
It indeed seems that admin rights are needed to use the auto mirroring feature.
However, you should be able to use the standard Git functionality to have multiple remotes. That is, typically you have a remote called 'origin' in your local Git repository to pull/push from/to your ESCET fork in GitLab. You can add a second remote for the
official ESCET Git repo in GitLab. You can then also pull from there, and then push it to your ESET fork. This way, you can work with all 3 repos (local one, official one in GitLab, your fork in GitLab).
Dennis
Van: escet-dev <escet-dev-bounces@xxxxxxxxxxx> namens Ferdie Reijnen <ferdie.reijnen@xxxxxxxxx>
Verzonden: zondag 11 april 2021 11:38
Aan: escet developer discussions <escet-dev@xxxxxxxxxxx>
Onderwerp: Re: [escet-dev] Contributing to ESCET
Hi Dennis,
I am now a bit lost. I don't think I am supposed to fork the repository each time I want to add a contribution?
It would be nice to add some instructions on the development page.
Kind regards,
Ferdie
Hi Ferdie,
> The only suggestion I have is to include what you expect in the "signed-off-by" field, it is not mentioned in the handbook you link, I had to google it.
> For the issues on GitLab. I'm not sure if it is intended, but I was unable to add labels [...]
> [...] or assign myself to the issue.
It seems we can only assign issues to committers. Maybe we can change that as well later. For now, just indicate in the comments that you're working on it.
Dennis
Hi Dennis,
Thanks for your quick response and for improving my contribution!
The guidelines are clear and I could easily follow them. I was not familiar with forking and then merging from the forked repository, but it was explained well. The only suggestion I have is to include what you expect in the "signed-off-by" field, it is
not mentioned in the handbook you link, I had to google it.
For the issues on GitLab. I'm not sure if it is intended, but I was unable to add labels or assign myself to the issue.
Kind regards,
Ferdie
Hi Ferdie,
Thanks for trying out the contribution guidelines. If you have any suggestions how to improve the guidelines, or insights into what works well or can be improved, please let us know. It's good to see you managed to create the issue and merge request.
I used this very first ever non-committer contribution to test out the process of extending your merge request. I found out how to get the merge request into my local Git, and add commits to it. It turns out this leads to a new branch 'merge-requets/28', as
it extends merge request !28 that you created. I then added a few commits, as part of reviewing your merge request. These don't appear in merge request !28 as that is from your branch in your own fork of the 'escet' repo on the Eclipse Foundation GitLab. Instead
I had to create my own merge request !29 instead. I'll close your merge request !28. Please take a look at merge request !29 to see whether you think my changes are OK.
It is a bit confusing that merge request !29 is now based on branch 'merge-request/28' for issue #25. We may have to find a better way for that.
Thank you for contribution!
Dennis
Hello everyone,
I contacted Albert to discuss the possibility of contributing some bug fixes to the ESCET project. He suggested to try to submit a contribution following the developer guidelines. I tried that with a small bug fix for a cif2cif transformation. There should
be a merge request for that submission now.
If I did anything wrong or my submission is incomplete please let me know.
Kind regards,
Ferdie
_______________________________________________
escet-dev mailing list
escet-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/escet-dev
_______________________________________________
escet-dev mailing list
escet-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/escet-dev
|
