Hi all,
I found some bugs (one at community authkey plugin and other at rest catalog api), and opened some issues about it today. I would like to commit these bug fix, but i need the permission to commit. How do i should proceed?
Thank you
The preferred way of submitting changes is a GitHub pull request. Here is the GeoTools guide, but the process is the same:
http://docs.geotools.org/latest/developer/procedures/pull_requests.html
http://docs.geotools.org/latest/developer/procedures/git.html
I make a new branch in my GitHub fork for each pull request. This is better than submitting pull requests from the master branch of my fork because it allows me to update it and to have multiple pull requests.
Pull requests must in the first instance target the master branch.
Kind regards,
Ben.
On 02/08/18 08:41, Luiz Felipe Caires wrote:
Hi all,
I found some bugs (one at community authkey plugin and other at rest catalog api), and opened some issues about it today. I would like to commit these bug fix, but i need the permission to commit. How do i should proceed?
Thank you
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <https://transient.nz/>
New Zealand
And please also make a Jira issue for each change. I like to use the Jira "export to XML" to make a nicely formatted title for my git commit message. I also put the Jira URL in the pull request description and link the pull request from the Jira issue. We can fix this for you after you have crested the Jira issue, if you lack Jira permissions.
Kind regards,
Ben.
On 02/08/18 09:45, Ben Caradoc-Davies wrote:
The preferred way of submitting changes is a GitHub pull request. Here is the GeoTools guide, but the process is the same:
http://docs.geotools.org/latest/developer/procedures/pull_requests.html
http://docs.geotools.org/latest/developer/procedures/git.htmlI make a new branch in my GitHub fork for each pull request. This is better than submitting pull requests from the master branch of my fork because it allows me to update it and to have multiple pull requests.
Pull requests must in the first instance target the master branch.
Kind regards,
Ben.On 02/08/18 08:41, Luiz Felipe Caires wrote:
Hi all,
I found some bugs (one at community authkey plugin and other at rest catalog api), and opened some issues about it today. I would like to commit these bug fix, but i need the permission to commit. How do i should proceed?
Thank you
------------------------------------------------------------------------------Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <https://transient.nz/>
New Zealand
I see that you have created the Jira issues. You can their titles (with Jira tags) as your commit messages.
On 02/08/18 09:49, Ben Caradoc-Davies wrote:
And please also make a Jira issue for each change. I like to use the Jira "export to XML" to make a nicely formatted title for my git commit message. I also put the Jira URL in the pull request description and link the pull request from the Jira issue. We can fix this for you after you have crested the Jira issue, if you lack Jira permissions.
Kind regards,
Ben.On 02/08/18 09:45, Ben Caradoc-Davies wrote:
The preferred way of submitting changes is a GitHub pull request. Here is the GeoTools guide, but the process is the same:
http://docs.geotools.org/latest/developer/procedures/pull_requests.html
http://docs.geotools.org/latest/developer/procedures/git.htmlI make a new branch in my GitHub fork for each pull request. This is better than submitting pull requests from the master branch of my fork because it allows me to update it and to have multiple pull requests.
Pull requests must in the first instance target the master branch.
Kind regards,
Ben.On 02/08/18 08:41, Luiz Felipe Caires wrote:
Hi all,
I found some bugs (one at community authkey plugin and other at rest catalog api), and opened some issues about it today. I would like to commit these bug fix, but i need the permission to commit. How do i should proceed?
Thank you
------------------------------------------------------------------------------Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <https://transient.nz/>
New Zealand