-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
github actions: consider using checkout@v2 #2683
Comments
Oh blah, We should try this again after actions/checkout#176 succeeds. |
Note also that To do a full clone, you do:
Alternatively, to make sure all the tags are fetched, see https://github.com/actions/checkout/blob/master/README.md#fetch-all-tags. I think that might work and still avoid fetching some of the history. I spent some time researching whether one could do a shallow clone and then fetch only the tag information, but that's not really how git works. Another possibility might be to have an initial job before all the board builds that does a complete clone and figures out the version info, and then passes that to the board builds, I guess in an environemtn variable. If they can't find a tag, they would use the info in the env var. That would save some clone time in the board jobs. But I don't think the clone time is all that significant compared to the actual build, so it's not clear it's worth the effort. |
Fixed by #2765. |
I am running into issues with PR #2666, which is repeatedly failing job re-runs due to "reference is not a tree" errors, even after merging from upstream. This is discussed in actions/checkout#23, which seems to indicate that we should upgrade to
checkout@v2
. I will try that in #2666.The text was updated successfully, but these errors were encountered: