On 9 Sep 2019, at 18:39, Hilaire <hilaire@drgeo.eu> wrote:
Le 08/09/2019 à 14:29, ducasse a écrit :
On 8 Sep 2019, at 14:22, Hilaire <hilaire@drgeo.eu <mailto:hilaire@drgeo.eu>> wrote:
hum, with some sort of luck I got it working as it should and in the process understood a bit the workflow. the workflow is your fork pharo then iceberg will clone you also commit to your working copy
when you are in trouble select repair the items are sorted in order of use probability
Where?
When you do repair.
My scenario is now: I want to resync my P8 installation with its remote state, so I can work on some fixes. How to?
When you "repair" your image, your repo is resync automatically. New commits from Pharo are pulled and when you push you push such changes too. I asked the same and in fact I never resync my fork explicitely since months.
you commit commit commit to your working copy then push to your fork then PR from your fork to pharo remote
In the tutorial, a few words explaining it could be useful to git newbies as me.
Hilaire
Le 08/09/2019 à 14:12, Hilaire a écrit :
What should I do now? -- Dr. Geo http://drgeo.eu
-- Dr. Geo http://drgeo.eu <http://drgeo.eu/>