Re: [Pharo-dev] contribution workflow

2019-02-01 Thread Ben Coman
On Tue, 22 Jan 2019 at 17:28, Guillermo Polito wrote: > Hi Ben, > > I'll just expand a bit on what Pavel said. > > On Mon, Jan 21, 2019 at 4:59 PM Ben Coman wrote: > >> I'm not sure how closely my contribution workflow matches the standard >> advertised, so just wanted to share it for feedback.

Re: [Pharo-dev] contribution workflow

2019-01-22 Thread Guillermo Polito
Hi Ben, I'll just expand a bit on what Pavel said. On Mon, Jan 21, 2019 at 4:59 PM Ben Coman wrote: > I'm not sure how closely my contribution workflow matches the standard > advertised, so just wanted to share it for feedback. I may remember > wrongly, but my understanding of the advertised

Re: [Pharo-dev] contribution workflow

2019-01-21 Thread Pavel Krivanek
You may simply clone your fork because the synchronization between it and the upstream repository is done automatically if you are contributing using Iceberg. When you are creating a branch from your image commit, Iceberg fetches the main Pharo repository to obtain information about the required

[Pharo-dev] contribution workflow

2019-01-21 Thread Ben Coman
I'm not sure how closely my contribution workflow matches the standard advertised, so just wanted to share it for feedback. I may remember wrongly, but my understanding of the advertised process was forking the "pharo-project/pharo" repo, then cloning from my fork. However I found it awkward to