Skip to content

Conversation

@asraa
Copy link
Collaborator

@asraa asraa commented Jul 21, 2025

See this failure
image

also removed the squash ready labeling

@asraa asraa requested a review from j2kun July 21, 2025 20:14
@j2kun j2kun added the pull_ready Indicates whether a PR is ready to pull. The copybara worker will import for internal testing label Jul 21, 2025
Copy link
Collaborator Author

@asraa asraa left a comment

Choose a reason for hiding this comment

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

@j2kun on the previous run it looked like I got an error message fetching the # of commits that the gh command wasn't run in a .git directory. i added a checkout step before that. could you try submitting another review?

Signed-off-by: Asra Ali <[email protected]>
@asraa
Copy link
Collaborator Author

asraa commented Jul 22, 2025

I got the same error and found out that there was a typo in the PR number env var and that is the issue. please approve me again! :P

@j2kun j2kun removed the pull_ready Indicates whether a PR is ready to pull. The copybara worker will import for internal testing label Jul 22, 2025
Signed-off-by: Asra Ali <[email protected]>
@j2kun
Copy link
Collaborator

j2kun commented Jul 22, 2025

gh: To use GitHub CLI in a GitHub Actions workflow, set the GH_TOKEN environment variable. Example:
  env:
    GH_TOKEN: ${{ github.token }}
Error: Process completed with exit code 4.

@asraa
Copy link
Collaborator Author

asraa commented Jul 23, 2025

ugh!! i looked online and secrets aren't accessible from forks until they have approval, so i would think this does have access? and i need a better debug message (is the repository secret just not working?!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants