Closed eloch216 closed 6 months ago
Update: maybe I misinterpreted the error message. I'm not totally sure what went wrong.
Judging from these two lines
nothing to commit, working tree clean
Error: Process completed with exit code 1.
I think the problem is that we are trying to commit changes when nothing has changed, because the script produced exactly the same result as it did when it was run on the source for the previous release. This will indeed produce an exit code of 1 from the commit command.
I suppose I could test this conjecture by running the script on the previous release version of BioCro and on this one and check that the results are exactly the same.
If this is indeed what is going on, then the main issue is that we get a reported run failure when there really is nothing wrong.
I suppose I could test this conjecture by running the script on the previous release version of BioCro and on this one and check that the results are exactly the same.
I did go ahead and run the script using the source versions of BioCro used for runs 2 through 4 of the Document quantities action. The result files are identical in all three cases.
I'm still thinking about what the best way is to avoid a workflow failing result in this case.
I guess it might not need to be a hotfix, since it seems this won't be an issue until there is another release.
There was an error in the recent automated workflow run related to the release of version 3.1.0:
https://github.com/biocro/biocro/actions/runs/8176197071/job/22355046093
It looks like another case where we have to provide a username and email address for git. I think this should probably addressed via a hotfix branch (?)
Update: maybe I misinterpreted the error message. I'm not totally sure what went wrong. For posterity, we have the following output from the "Commit updates and push to target (documentation) repository" step: