Add native local Git repository awareness - #541
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| { | ||
| bool operator()(const std::wstring& lhs, const std::wstring& rhs) const noexcept | ||
| { | ||
| return _wcsicmp(lhs.c_str(), rhs.c_str()) < 0; |
| workingDirectory, | ||
| { | ||
| L"-c", | ||
| L"core.fsmonitor=false", |
| L"-c", | ||
| L"core.fsmonitor=false", | ||
| L"-c", | ||
| L"core.quotepath=false", |
| *root, | ||
| { | ||
| L"-c", | ||
| L"core.fsmonitor=false", |
| L"-c", | ||
| L"core.fsmonitor=false", | ||
| L"-c", | ||
| L"core.quotepath=false", |
| TEST_CLASS(GitProcessRunnerTests); | ||
|
|
||
| TEST_METHOD(RejectsRelativeOrMissingExecutable); | ||
| TEST_METHOD(CapturesOutputWithoutAWindow); |
| VERIFY_IS_FALSE(GitProcessRunner{ std::filesystem::temp_directory_path() / L"missing-git.exe" }.IsValid()); | ||
| } | ||
|
|
||
| void GitProcessRunnerTests::CapturesOutputWithoutAWindow() |
| TEST_METHOD(DoesNotInferNestedWorktreeFromParentCache); | ||
| TEST_METHOD(EvictsUnreferencedCacheAfterGracePeriod); | ||
| TEST_METHOD(NotifiesMultipleSubscribersIndependently); | ||
| TEST_METHOD(SerializesSummaryOnlyProtocolSchema); |
| std::string errors; | ||
| std::istringstream stream{ json }; | ||
| VERIFY_IS_TRUE(Json::parseFromStream(reader, stream, &event, &errors)); | ||
| VERIFY_ARE_EQUAL(std::string{ "repo_state_changed" }, event["method"].asString()); |
check-spelling-bot Report
|
| Dictionary | Entries | Covers | Uniquely |
|---|---|---|---|
| cspell:csharp/csharp.txt | 32 | 2 | 2 |
| cspell:aws/aws.txt | 232 | 2 | 2 |
| cspell:fonts/fonts.txt | 536 | 1 | 1 |
Consider adding to the extra_dictionaries array (in the .github/actions/spelling/config.json file):
"cspell:csharp/csharp.txt",
"cspell:aws/aws.txt",
"cspell:fonts/fonts.txt",
To stop checking additional dictionaries, put (in the .github/actions/spelling/config.json file):
"check_extra_dictionaries": []Pattern suggestions ✂️ (1)
You could add these patterns to .github/actions/spelling/patterns/2e35860a31c96a8802221ad7db0ba49d4e64ebe2.txt:
# Automatically suggested patterns
# hit-count: 1 file-count: 1
# container images
image: [-\w./:@]+
Alternatively, if a pattern suggestion doesn't make sense for this project, add a # to the beginning of the line in the candidates file with the pattern to stop suggesting it.
Warnings and Notices ⚠️ (2)
See the 📂 files view, the 📜action log, 👼 SARIF report, or 📝 job summary for details.
| Count | |
|---|---|
| ℹ️ candidate-pattern | 1 |
| 54 |
See
✏️ Contributor please read this
By default the command suggestion will generate a file named based on your commit. That's generally ok as long as you add the file to your commit. Someone can reorganize it later.
If the listed items are:
- ... misspelled, then please correct them instead of using the command.
- ... names, please add them to
.github/actions/spelling/allow/names.txt. - ... APIs, you can add them to a file in
.github/actions/spelling/allow/. - ... just things you're using, please add them to an appropriate file in
.github/actions/spelling/expect/. - ... tokens you only need in one place and shouldn't generally be used, you can add an item in an appropriate file in
.github/actions/spelling/patterns/.
See the README.md in each directory for more information.
🔬 You can test your commits without appending to a PR by creating a new branch with that extra change and pushing it to your fork. The check-spelling action will run in response to your push -- it doesn't require an open pull request. By using such a branch, you can limit the number of typos your peers see you make. 😉
If the flagged items are 🤯 false positives
If items relate to a ...
-
binary file (or some other file you wouldn't want to check at all).
Please add a file path to the
excludes.txtfile matching the containing file.File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.
^refers to the file's path from the root of the repository, so^README\.md$would exclude README.md (on whichever branch you're using). -
well-formed pattern.
If you can write a pattern that would match it,
try adding it to thepatterns.txtfile.Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.
Note that patterns can't match multiline strings.
2 participants
Summary of the Pull Request
References and Relevant Issues
Detailed Description of the Pull Request / Additional comments
Validation Steps Performed
PR Checklist