use DEBUG flag instead of CI #358
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
|
Hi @Dexus, could you please have a look? |
|
If you want to change it, the GitHub workflow should be considered as well. If the change is made, I can accept it. |
I made requested changes #373 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
CI is set to true in CI/CD tools such as Bitbucket pipelines. That results in excessive debug log if pem library is used in scripts that run in CI/CD of other projects, e.g. when pem library is used in tests that are running in a Bitbucket pipeline.
It would be therefore better to use a different flag than CI to control when debug logs are produced. This PR suggests DEBUG flag.