It turns out that I can assign issues to you once you've added a comment to them, using a very well hidden feature. I did that for several issues where you commented.
I still can't assign you to the issues where you provided a merge request but did not comment on the issue. E.g. #25, #37, #47, #58, #60.
Apparently, I should be able to change permissions to make you a reporter on the project, allowing you assign yourself to issues and add issue labels. However, there appears to be a problem with
https://github.com/EclipseFdn/eclipsefdn-github-sync/issues/143,
meaning I don't have the required permissions yet to do so.
To be continued...
Dennis
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
