There is a new Pharo build available!
The status of the build #132 was: FAILURE.
The Pull Request #2267 was integrated:
"22887-TonelWritercreateDefaultOrganizationFrom-can-return-string"
Pull request url: https://github.com/pharo-project/pharo/pull/2267
Issue Url:
There is a new Pharo build available!
The status of the build #14 was: FAILURE.
The Pull Request #2276 was integrated: " Context>>methodReturnContext now uses
Context>>home instead of repli…"
Pull request url: https://github.com/pharo-project/pharo/pull/2276
Issue Url:
There is a new Pharo build available!
The status of the build #15 was: FAILURE.
The Pull Request #2278 was integrated: "Added tests about Context>>home and
Context>>activeHome"
Pull request url: https://github.com/pharo-project/pharo/pull/2278
Issue Url:
There is a new Pharo build available!
The status of the build #16 was: FAILURE.
Could not extract further issue information from commit message: Merge branch
'Pharo7.0' into Pharo8.0
# Conflicts:
# bootstrap/scripts/envversion.sh
# bootstrap/scripts/transform_32_into_64.sh
Build
There is a new Pharo build available!
The status of the build #133 was: FAILURE.
The Pull Request #2285 was integrated:
"22903-backport-to-P70fixes-on-bootstrap-scripts"
Pull request url: https://github.com/pharo-project/pharo/pull/2285
Issue Url: https://pharo.fogbugz.com/f/cases/22903
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
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
