Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: spelling: update to 0.0.16a; update advice #5922

Merged
merged 1 commit into from
May 28, 2020

Conversation

jsoref
Copy link
Contributor

@jsoref jsoref commented May 15, 2020

Summary of the Pull Request

Updates the check spelling action to 0.0.16-a

  • update advice -- sample -- I really do encourage others to adjust it as desired
  • rename expect (there are consumers who were not a fan of the whitelist nomenclature)
  • prune stale items
  • some patterns improvements to reduce the number of items in expect

⚠️ Anyone with an inflight addition of a new file to the whitelist directory will be moderately unhappy as the action would only use items from there if it didn't find expect (and this PR includes the rename).

References

PR Checklist

  • Closes #xxx
  • CLA signed. If not, go over here and sign the CLA
  • Tests added/passed
  • Requires documentation to be updated
  • I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments

Runs should be ~30s faster.

I was hoping to be able to offer the ability to talk to the bot, but sadly that feature is still not quite ready -- and I suspect that I may want to let projects opt in/out of that feature.

Validation Steps Performed

The commands were never cmd/psh friendly. This iteration is designed to make it easier for a bot to parse and eventually do the work in response to a GitHub request, sadly that feature is behind schedule.

* rename expect
* prune stale items
* add some patterns
@@ -0,0 +1,13 @@
The contents of each `.txt` file in this directory are merged together.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a rename, but Git thinks it's too different to qualify.

@zadjii-msft zadjii-msft added the Needs-Second It's a PR that needs another sign-off label May 20, 2020
@ghost ghost requested review from miniksa, carlos-zamora and leonMSFT May 20, 2020 19:51
@miniksa
Copy link
Member

miniksa commented May 27, 2020

@jsoref, can you resolve conflicts here whenever you get a chance?

Copy link
Member

@DHowett DHowett left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you for this; also, thanks for the rename 😄 I definitely prefer expect

@jsoref
Copy link
Contributor Author

jsoref commented May 27, 2020

I started resolving the conflicts earlier today. Lemme finish it now...

@@ -224,11 +203,8 @@ CARETBLINKINGENABLED
CARRIAGERETURN
cascadia
catid
carlos
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so in this case, we preemptively added Carlos/Zamora because he keeps getting flagged on his specifications 😄

Copy link
Contributor Author

@jsoref jsoref May 27, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You want to add him in the dictionary/ directory -- specifically dictionary/names.txt

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, great. thanks.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there something I can do to the advice to make that clearer? -- Since we're trying to update that file here...

@jsoref jsoref force-pushed the spell-check branch 3 times, most recently from 66334a6 to 78df00d Compare May 27, 2020 23:56
@jsoref
Copy link
Contributor Author

jsoref commented May 27, 2020

(I really was trying to avoid this having lots of force pushes, I did a whole bunch where I only force pushed the test commit and not the actual commit... But, sigh.)

Ok. All done.

@j4james : I hope this doesn't cause your pattern update too much pain. I didn't end up changing that line, although at some point I really do want to update [Ll]? to [Ll]{0,2} -- to handle long long.

@DHowett
Copy link
Member

DHowett commented May 28, 2020

We squash the HECC out of pull requests, so if it's easier for you to go wild and commit stuff like zadjii-msft does, do!

image

@jsoref
Copy link
Contributor Author

jsoref commented May 28, 2020

Mostly I'm trying to avoid burning CPU cycles on the build system; partially it's I don't really need people to see my embarrassing mistakes; partially I like the idea of making commits that only part of the environment sees -- specifically it's sufficient for me to push my commits on a branch to GitHub to get the spell checker to run -- I don't need to update the PR itself for that -- this is a designed feature.

n.b.: I'm working on getting act to work so one could easily run the spell checker locally. It involves playing w/ Go and a certain amount of divination... I'm hoping to have that working + well documented by the next release or so.
I really want to get the comment to apply feature finished too. I might try to sprint on it over the weekend....

@j4james
Copy link
Collaborator

j4james commented May 28, 2020

@j4james : I hope this doesn't cause your pattern update too much pain. I didn't end up changing that line, although at some point I really do want to update [Ll]? to [Ll]{0,2} -- to handle long long.

No worries. I expect I'll have to rebase that PR a few more times anyway. And I forgot you asked to do the long long update. I can still add that next time I rebase if you want.

@jsoref
Copy link
Contributor Author

jsoref commented May 28, 2020

@DHowett: well, squash / rebase away ;-)

@zadjii-msft zadjii-msft added the AutoMerge Marked for automatic merge by the bot when requirements are met label May 28, 2020
@ghost
Copy link

ghost commented May 28, 2020

Hello @zadjii-msft!

Because this pull request has the AutoMerge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost
Copy link

ghost commented May 28, 2020

Apologies, I am afraid I am encountering technical difficulties that might have hampered my ability to assist with merging this pull request. I will continue to try to assist if there are further changes to this pull request.

@zadjii-msft zadjii-msft merged commit cc472c2 into microsoft:master May 28, 2020
@zadjii-msft
Copy link
Member

Well that was weird. Anywho, thanks again for the contribution!

@jsoref jsoref deleted the spell-check branch May 28, 2020 14:39
jelster pushed a commit to jelster/terminal that referenced this pull request May 28, 2020
<!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? -->
## Summary of the Pull Request

Updates the check spelling action to [0.0.16-a](https://github.com/check-spelling/check-spelling/releases/tag/0.0.16-alpha)
* update advice -- [sample](jsoref@57fc13f#commitcomment-39489723) -- I really do encourage others to adjust it as desired
* rename `expect` (there are consumers who were not a fan of the `whitelist` nomenclature)
* prune stale items
* some `patterns` improvements to reduce the number of items in `expect`


<!-- Other than the issue solved, is this relevant to any other issues/existing PRs? --> 
:warning: Anyone with an inflight addition of a new file to the `whitelist` directory will be moderately unhappy as the action would only use items from there if it didn't find `expect` (and this PR includes the rename).

## References

<!-- Please review the items on the PR checklist before submitting-->
## PR Checklist
* [ ] Closes #xxx
* [x] CLA signed. If not, go over [here](https://cla.opensource.microsoft.com/microsoft/Terminal) and sign the CLA
* [ ] Tests added/passed
* [ ] Requires documentation to be updated
* [ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

<!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here -->
## Detailed Description of the Pull Request / Additional comments
Runs should be ~30s faster.

I was hoping to be able to offer the ability to talk to the bot, but sadly that feature is still not quite ready -- and I suspect that I may want to let projects opt in/out of that feature.

<!-- Describe how you validated the behavior. Add automated tests wherever possible, but list manual validation steps taken as well -->
## Validation Steps Performed

* I added a commit with misspellings: jsoref@57fc13f ❌  and ran the command it suggested (in bash). 
* The commit [itself passes its own testing](jsoref@78df00d) ✔️ 

The commands were never `cmd`/`psh` friendly. This iteration is designed to make it easier for a bot to parse and eventually do the work in response to a GitHub request, sadly that feature is behind schedule.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AutoMerge Marked for automatic merge by the bot when requirements are met Needs-Second It's a PR that needs another sign-off
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants