Astares

might be fixed with https://github.com/pharo-project/pharo/pull/16562

Fix or ban or ignore them

There is no downside - but using labels is a little bit strange. I would vote to **use the Milestone** now properly as this is a clear concept in software,...


This needs to be solved for the **BaselineOfNewTools** (which is hosted in https://github.com/pharo-spec/NewTools). Here we need to adopt specifically the one in the Pharo13 branch. And we should not hard...

We should fix it in Pharo13 with ```Smalltalk sindarin: spec spec baseline: 'Sindarin' with: [ spec repository: (self class environment at: #BaselineOfPharo) scriptableDebuggerRepository; loads: 'default' ] ```

@kderichs thanks

I think it happened only when I used the "Duplicate" function to duplicate a class and then late want to commit it together with changes on the original class. Maybe...

As the message said: you need to setup GH credentials/keys first

Here is the list: - HashTesterTest->#'SUnit-Core' - BehaviorWithCompilerTest->#'Kernel-Tests-WithCompiler' - RuntimeSyntaxErrorTest->#'Kernel-Tests-WithCompiler' - SelfEvaluatingObjectTest->#'Kernel-Tests-WithCompiler' - DiskFileAttributesTest->#'FileSystem-Tests-Attributes' - FileAttributesPluginPrimsTest->#'FileSystem-Tests-Attributes' - FileReferenceAttributeTest->#'FileSystem-Tests-Attributes' - RGPackageDefinitionTest->#'Ring-Definitions-Tests-Containers' - CoverageCollectorTest->#Coverage - RBTestAsDataForExtractSetupTransformationTest->#'Refactoring-DataForTesting' - MetacelloCoreIssue125TestCase->#'Metacello-TestsCore' - MetacelloCoreSymbolicVersionTest->#'Metacello-TestsCore' - MetacelloCoreVersionQueryTestCase->#'Metacello-TestsCore'...