Repository navigation
Spell check - #645
Spell check#645
Conversation
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
Josh Soref (jsoref)
left a comment
There was a problem hiding this comment.
It's possible to split the spelling fixes from the spell-check action, but it's important to land the spell-checker w/o letting there be too much drift between its PR base and master -- it's bad to land it if there have been typos introduced since its base (as all new PRs from its landing will have confusing failures).
For reference, this PR gets a ✅ : jsoref@4ad3543
| <data name="SourceListField" xml:space="preserve"> | ||
| <value>Veld</value> | ||
| <comment>The name of a peice of information about a source.</comment> | ||
| <comment>The name of a piece of information about a source.</comment> |
There was a problem hiding this comment.
It's possible I should drop the localization comment changes (I never know what the policy is)
There was a problem hiding this comment.
Certainly the localization comments can be updated; they will just be overwritten by future changes if needed.
|
|
||
| CompletionTestCommand command; | ||
| command.SubCommandNames = { "car", "cart", "cartesion", "carpet" }; | ||
| command.SubCommandNames = { "car", "cart", "cartesian", "carpet" }; |
There was a problem hiding this comment.
This change is probably the biggest
| { | ||
| // If moved to C++20, this can be replaced with standard library implementations. | ||
| void OutputTimepoint(std::ostream& stream, const std::chrono::system_clock::time_point& time) | ||
| void OutputTimePoint(std::ostream& stream, const std::chrono::system_clock::time_point& time) |
There was a problem hiding this comment.
Given that the underlying type is time_point, it made sense to me to use this capitalization
| return "winget upgrade --all completed with failures"; | ||
| default: | ||
| return "Uknown Error Code"; | ||
| return "Unknown Error Code"; |
There was a problem hiding this comment.
This could be a cli api change
| if (!availablePackage) | ||
| { | ||
| AICLI_LOG(Repo, Warning, << " Appropriate available package could not be determined, setting availablility state to unknown"); | ||
| AICLI_LOG(Repo, Warning, << " Appropriate available package could not be determined, setting availability state to unknown"); |
There was a problem hiding this comment.
This may be a cli api change
| // DisplayVersion | ||
| // Version | ||
| // MajorVerison, MinorVersion | ||
| // MajorVersion, MinorVersion |
There was a problem hiding this comment.
Google Sheets suggested Verizon
There was a problem hiding this comment.
Major Verizon
A lot of these changes are my extremely common typos that I failed to correct. I'm sure that some sort of ML (or just analysis of qwerty) could probably figure out that one of my fingers jumps the gun on the others occasionally.
Add JsonCppLib
Revert spelling changes to JsonCppLib.
| - uses: actions/checkout@v2.0.0 | ||
| with: | ||
| fetch-depth: 5 | ||
| - uses: check-spelling/check-spelling@0.0.16-alpha |
There was a problem hiding this comment.
check-spelling/check-spelling@0.0.16-alpha [](start = 12, length = 42)
I'm not familiar with GitHub Actions.
- Will we need to update this version manually to keep up with new releases?
- Do we need to do something to manage the secrets.GITHUB_TOKEN? Or is that automatically done by the Actions infrastructure?
- Generally, are there any other actions we need to take to manage this (beyond excludes, patterns, etc. for new changes)?
Thanks for your work here.
There was a problem hiding this comment.
- In theory Dependabot (@dependabot) can tell you about updates, but for the near term, I'll probably make the PR myself.
- The
GITHUB_TOKENis automatic https://docs.github.com/en/free-pro-team@latest/actions/reference/authentication-in-a-workflow#about-the-github_token-secret - Beyond that and trying to avoid merging things with spelling errors (if the main branch is unhappy, anyone who branches from that point will be unhappy / confused), no.
- There is the option to add an advice.txt file which is included in the message the bot leaves, but that's totally tunable and that's really something you'll work through as a project.
- Technically GitHub has a budget for actions, it's theoretically possible for someone to run into this limit, I suspect that Microsoft has a reasonably large budget and you won't notice (certainly microsoft/terminal hasn't complained) -- if someone publicly runs into this, I'd love to hear about it. (Generally other actions are more expensive than this one -- which runs at about 1 minute and is thus billed as 1-2 units.) Most likely if a project like yours hits something like this, it means you have a bunch of files that should be ignored that you aren't ignoring (one project I'm looking at takes ~20 minutes to scan). -- If this becomes a problem for some other project in the future, I'll probably write some code so that it tries to scan only changed files instead of the whole repository.
There was a problem hiding this comment.
Thanks for the info, I agree that only checking changed files seems like a good optimization opportunity.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
closes #559
This enables https://github.com/marketplace/actions/check-spelling
Microsoft Reviewers: Open in CodeFlow