use debug logs #7
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hey, we have a very large repository and each folder (or file) has a code owner.
This causes the action to generate a lot of logs, so that the important "File not covered by CODEOWNERS: ..." logs are no longer displayed in the overview.
GitHub warning from the action:
This step has been truncated due to its large size. View the raw logs from the menu once the workflow run has completed.You can still view the logs via the “raw logs,” but it would be nicer to see them directly in the first overview.
What do you think about setting all other logs to the debug log level?
Tested from my develop branch:
Note: This PR does not include the build
dist/index.js