fix #13998: Add script for pulling latest simplecpp version

[ludviggunne]

[firewave]

• a script just to help you copy 2 files? I think it's pretty quick and easy to do manually.

This way it documents what to do and could be easily run without much copy and paste.

A additional step could be to automatically generate a Cppcheck PR when a new tag is created in the simplecpp repo. Which would leverage the script.

[danmar]

This way it documents what to do and could be easily run without much copy and paste.

Documentating the release process etc is valuable. However plain text is less "cryptic". Imho a python script would also be less "cryptic". I.e. instead of head -1 | cut -f2 it is better with corresponding python code.

This way it documents what to do and could be easily run without much copy and paste.

I don't know I still feel I loose a bit of control here. Many things can go wrong if it's used wrongly. Ensure that it can't be used wrongly.

It will always blindly pick latest release... so if I tag a release candidate then the release candidate will be picked.

It would probably be better to commit automatically to enforce that the commit message contains the tag that is used.

And I think some better checking could be good before any files are copied at all.

• Ensure that current branch is main branch. Not some feature branch.
• Ensure that main branch is uptodate. No extra commits/changes.
• => the commit should only contain the expected changes no unrelated changes.
• whatever other error conditions we can imagine..

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[firewave]

See https://github.com/danmar/cppcheck/pull/7659 for way to leverage this.