Skip to content
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

Automatically set logging variables when debuging a failing GHA #193

Merged
merged 3 commits into from
Jul 2, 2024

Conversation

hadley
Copy link
Member

@hadley hadley commented Jun 28, 2024

Fixes #175

@hadley hadley requested a review from cderv June 28, 2024 21:06
Copy link
Collaborator

@cderv cderv left a comment

Choose a reason for hiding this comment

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

FWIW there is also ACTIONS_STEP_DEBUG=1 that could be set manually.

I believe here we are targetting the failed job re-run and this will set both ACTIONS_STEP_DEBUG and ACTIONS_RUNNER_DEBUG, so all good.

This is a nice idea. I should see to do the same king of things in Quarto to activate verbose when this is set.

@hadley
Copy link
Member Author

hadley commented Jul 2, 2024

Hmmm, I think ACTIONS_STEP_DEBUG is probably the better env var to use.

@hadley hadley merged commit 30ed781 into main Jul 2, 2024
13 checks passed
@hadley hadley deleted the gha-debug branch July 2, 2024 13:23
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.

Automatically set various logging flags when debugging on GHA
2 participants