Jakob Reschke

Yep, so you would use this instead of %APPDATA%. The security concern is unchanged.

Because I did not want to override the existing methods and functionality if it is already present. Now that Squeak 6.0 is here I could reconsider.

Since this is in FileSystem-Git, not in Squot, I would have to create compatibility packages there in the first place. But wait, maybe the SquotCompatibility-SqueakCommon package is actually mislabelled now,...

Indeed, only FileSystem-Git code uses things from SquotCompatibility-SqueakCommon. With the old name Pharo-Compatbility it did not matter which code used it. :-) So I could rename that package. But for...

Would be a good idea, yes. Can you write the script that will create the archive, please?

What's the preferred place? Squeak Help or GitHub wiki? (SWE topic proposal: Squeak-Help--GitHub-Wiki Synchronizer)

There should be no nodes without an artifactDiff. Did you actually encounter one that did not have one? Then I would rather like to fix that.

Especially the latter two points would consume quite an amount of screen real estate, and the branch list is rather narrow by default today. It might require another tool that...

GitHub also only knows the destination branch because you tell it which one to use, or otherwise the "main" branch as configured in the GitHub project (for this Squot project,...

Exactly what you concluded. Now actually I would like to better understand why `ref:` returned nil here, and avoid that from entering the collection in the first place. Refs shouldn't...