feat: update unicode characters #252
Draft
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
|
@suppo01, could you please investigate why most of the checks failed? Understanding any specific issues or configuration challenges would be helpful. While the PR introduces a small but likely impactful change, we’ll need to resolve these issues before proceeding. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR focuses on resolving the unicode decode error run by gatorgrade on Windows.
What is the current behavior?
A unicode decode error is thrown on Windows machines.
What is the new behavior if this PR is merged?
The error will be resolved and correctly run gatorgrader checks on Windows for gatorgrade.
Other information
This PR has:
This PR is a small change
that fixes #251
Developers
@suppo01