Merged
Conversation
added 2 commits
June 19, 2024 12:35
This will add a layer of abstraction around the GitHub API interactions that write to the API (i.e., stuff affected by `DRY_RUN`. This helps test the tool without actually writing to GitHub. An additional logging variable was added, `LOG_LEVEL` that allows the user to specify how verbose (higher = less verbose) the tool will be when determing which messages to display. The default is 20 (i.e., INFO); 10 would correspond to DEBUG while 50 would correspond to CRITICAL. The documentation and sample env file were updated.
This adds a note to the README about what this tool doesn't do (i.e., it doesn't affect organization membership, nor does it affect repository settings) and a note about using team synchronization with GHEC accounts.
Contributor
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
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
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.
This will add a layer of abstraction around the GitHub API interactions
that write to the API (i.e., stuff affected by
DRY_RUN. This helpstest the tool without actually writing to GitHub.
An additional logging variable was added,
LOG_LEVELthat allows theuser to specify how verbose (higher = less verbose) the tool will be
when determing which messages to display. The default is 20 (i.e.,
INFO); 10 would correspond to DEBUG while 50 would correspond to
CRITICAL.
The documentation and sample env file were updated.