This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
Spelling #72
Merged
Spelling #72
Conversation
This file contains 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
Signed-off-by: Josh Soref <[email protected]>
Signed-off-by: Josh Soref <[email protected]>
|
The failed E2E tests are running in |
jidicula
approved these changes
Jun 19, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What are you trying to accomplish?
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/gh-actions-cache/actions/runs/5301784795#summary-14349697639
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/gh-actions-cache/actions/runs/5301784834#summary-14349697810
What approach did you choose and why?
Anything you want to highlight for special attention from reviewers?