add git hash to metadata output

[BenWibking]

Description

This adds the git commit hash to metadata.yaml for plotfiles and checkpoints. This allows users to track the exact provenance of simulation outputs.

Related issues

Closes #852.

Checklist

Before this pull request can be reviewed, all of these tasks should be completed. Denote completed tasks with an x inside the square brackets [ ] in the Markdown source below:

• I have added a description (see above).
• I have added a link to any related issues (if applicable; see above).
• I have read the Contributing Guide.
• I have added tests for any new physics that this PR adds to the code.
• (For quokka-astro org members) I have manually triggered the GPU tests with the magic comment /azp run.

[BenWibking]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[markkrumholz]

Changes generally look fine, but I have a question about how you expect the warning about untracked changes to work for people outside our research group, who do not have write access to our repo, but who will presumably want to create their own problem generators. Is the idea that they will create their own forks of the repo into which to check their problem setups, and the track changes warning will then be checked against their fork? Is the expectation that they should submit their problem setups to the main repo?

[BenWibking]

Changes generally look fine, but I have a question about how you expect the warning about untracked changes to work for people outside our research group, who do not have write access to our repo, but who will presumably want to create their own problem generators. Is the idea that they will create their own forks of the repo into which to check their problem setups, and the track changes warning will then be checked against their fork? Is the expectation that they should submit their problem setups to the main repo?

I think we can be agnostic as to what branch the changes are committed to. As long as the changes have been committed (even only locally), then the resulting git hash can be used to uniquely identify what version of the source code produced it, since it's unique.

[BenWibking]

@markkrumholz Let me know if this clarifies things.

[markkrumholz]

@markkrumholz Let me know if this clarifies things.

Looks good to me.

[markkrumholz]

Sorry, meant to close the conversation, not the PR.

[sonarqubecloud]

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