Authorize requests to GitHub API in Run CBMC proofs
workflow
#1057
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available: N/A - The
Run CBMC proofs
jobs have been intermittently failing as of late (see, for example, this CI run). This appears to happen while parsing the requests done to the GitHub API (requests done withcurl
, parsing done withjq
).The issue is similar to the one in this discussion. As mentioned in the last comment, it's possible that requests to the GitHub API are being rate-limited since they're not being authorized.
Description of changes: This PR changes the
Run CBMC proofs
workflow so that it authorizes the requests to the GitHub API with the secret available through${{ secrets.GITHUB_TOKEN }}
. I've followed the example shown in GitHub documentation here. Unfortunately, changes to GA workflows cannot be reliably test, especially considering that the failure is intermittent.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.