Ah yes that's the tool. Generally speaking if you plan to contribute to the repo very frequently being a contributor will allow you to commit directly since in most cases you will be familiar with the repo and know what you doing. I see a pull request as a way to moderate commits by people that cannot be trusted or that are not regular contributors. In case of a pull request it's the workflow that Peter describes but I prefer an addition step, open an issue or link your request to an issue. It make tracking pull requests easier and cleaner. On Fri, 22 Jul 2016 at 10:12, Peter Uhnak <i.uhnak@gmail.com> wrote:
On Fri, Jul 22, 2016 at 11:55:46AM +0800, Ben Coman wrote:
I'm not sure what the roadmap is for git integration, but just a use case that occurs to me while I work "a bit with git" for the first time from Pharo.
I install a project via a Baseline from git and makes a small improvement. What is the easiest way to contribute back? I can't push back to the personal repo I downloaded from, so the easiest thing would be a single menu item to: 1. Fork original repository 2. Push current in-Image code to a new branch in that fork.
Maybe even... 3. Issue a pull request to the original repository.
This is indeed the idiomatic way to contribute on GitHub.
1. fork 2. install _your fork_ with gitfiletree/remote git repo 3. make an improvement (you can use master branch, since it's your repo, but that's a detail) 4. issue a pull request
Maybe IceBerg (https://github.com/npasserini/iceberg) could have some nice interface for this eventually.
Peter
cheers -ben