You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the upload-archive job of the release CI, git is seemingly no longer available to use since we archived. I suppose when we archive it, and then store it, it does not preserve git history. A warning for a run can be seen here.
Apart from pushing to the stable branch in the step shown, it is useful to have git at this stage as we'd like to forward the description of the git tag to the release notes.
The text was updated successfully, but these errors were encountered:
Hmm, seems like the logs for the nightly releases are now gone. Perhaps some thing changed in an update of Github actions? I do not think any of the recent changes in release.yml should have any effect on the presence of .git/.
Regardless, the absence of .git/ does not seem to trigger an error, it just silently fails.
In the
upload-archive
job of the release CI, git is seemingly no longer available to use since we archived. I suppose when we archive it, and then store it, it does not preserve git history. A warning for a run can be seen here.Apart from pushing to the stable branch in the step shown, it is useful to have git at this stage as we'd like to forward the description of the git tag to the release notes.
The text was updated successfully, but these errors were encountered: