Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[FR] Flag commit hash as "dirty" in UI if git repo has local changes #1912
Describe the proposal
Add a flag in UI (and database, if necessary) that identifies a commit hash as "dirty" if the git repository has local changes.
Version: 1.3.0 (installed via pip)
In this situation, the first run is reproducible, the second one is not. In the UI both runs are displayed with the same (i.e. the most recent) commit hash. This gives the impression that both experiments where run with exactly the same code, which is not true. As far as I could find, there seems to be no way to identify the "dirty" second run. Please let me know if I missed something.
Other tools such as omniboard for sacred or neptune show a flag that identifies the "dirty" run as such. This does not make the run reproducible, but it does at least alert the user that this is the case.
I agree with the issue, but not necessarily with the proposed solution. The reason for this is, that the second run is still not reproducible - we know its 'dirty', but we still don't know what changed.
If you insist on running this, maybe run
or something similar.
I agree, it does not solve the actual reproducibility issues. I like your proposal. I see two possible ways that one could go with the flag
I do prefer (1), however I do see a risk that this might annoy some users, because of perceived overhead.