Silvano Cerza

> I would suggest that only files that are modified and that the "functional" commit with the code changes be separated from another commit for pretty printing in that file...

I see I stirred something with formatting. 😅 Just to be clear that I'm just talking about formatting of C/C++ code in C/C++ files as of now. `sclang` files are...

> Yes, sclang formatting is a complicated topic, because it is (also) about artistic style. @telephon Makes totally sense and I see no issue with that. Introducing a formatter shouldn't...

@dyfer First of all I realised while writing this that I didn't commit the new release workflow. 🤦 I pushed it now. > Things can certainly be changed, but I...

@dyfer > I get the ambiguous part. The mechanics of it are not ideal, maybe. HOWEVER what I'm saying is that it worked _correctly_, as far as I remember, for...

@capital-G I'd like to add a pre-commit hook for this check too. Ideally the [`actionlint-docker`](https://github.com/rhysd/actionlint/blob/9fe5134f105bcb3687cd5c38466b15458b9bb65e/.pre-commit-hooks.yaml#L10-L16) one to avoid the burden on contributors. In any case it will be skipped if...

> IIRC pre-commit will install the hooks once they are declared and not when they are actually used - I think this could introduce docker as a dev dependency which...

@capital-G I consider config files in json/yaml to be code. My point is that you don't always need to run the whole CI and test suite if you edit a...

Separate Arm and x86 builds are better in my opinion. The binaries created are much smaller. Not sure if the build process would be easier though. I can give it...

Somewhat related to this but I couldn't find a thorough guide on building the project on different platforms and architecture. I kinda tried to follow the CI steps to build...