Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

fix: update tokenless branch logic #1650

Merged
merged 12 commits into from
Nov 15, 2024
Merged

Conversation

thomasrockhu-codecov
Copy link
Contributor

No description provided.

action.yml Fixed Show fixed Hide fixed
action.yml Fixed Show fixed Hide fixed
action.yml Fixed Show fixed Hide fixed
@thomasrockhu-codecov thomasrockhu-codecov merged commit 2e2a9c6 into main Nov 15, 2024
13 checks passed
@thomasrockhu-codecov thomasrockhu-codecov deleted the th/fix-tokenless-branches branch November 15, 2024 12:50
env:
CC_BRANCH: ${{ inputs.override_branch }}
GITHUB_EVENT_PULL_REQUEST_HEAD_LABEL: ${{ github.event.pull_request.head.label }}
GITHUB_EVENT_PULL_REQUEST_REPO_FULL_NAME: ${{ github.event.pull_request.repo.full_name }}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Greetings.

I am not sure where did full_name come from. This event variable does not exist in the documentation, and it is also not outputting anything when I am testing it in my repositories (not forks).

And due to that fact, the following check here:
if [ -z "$CC_BRANCH" ] && [ -z "$CODECOV_TOKEN" ] && [ "${GITHUB_EVENT_PULL_REQUEST_REPO_FULL_NAME}" != "$GITHUB_REPOSITORY"
is always false when I am upgrading to codecov-action v5, which leads to some side effects with the token check.

So, unless I am missing something, I think it is a bug.

Best,
Rust

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@amureki there was a slight bug, but that has been fixed in 5.0.3. As for why is it empty, it seems that this variable when not from a fork will be empty, thus the issue you were seeing.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, got it @thomasrockhu-codecov
Thank you for the explanation and resolving the issue!

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants