Use apiURL to determine whether to use the token #1615
Closed
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.
The action includes this check to determine whether to include the token in the request:
The intention is to only include the token if we are fetching from the same instance, to avoid leaking tokens.
However, the
codeqlURL
in this check will refer to the APIurl
to use to download the release. For example:https://api.github.com/repos/myrepo/codeql-action/releases/assets/
However, the
apiDetails.url
refers to the instance URL, e.g.https://github.com
, which means the check will always fail. We therefore need to use theapiDetails.apiURL
to get the appropriate comparison.Merge / deployment checklist