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

Spell Check GH Action #31

Closed
wants to merge 2 commits into from
Closed

Conversation

TidbitsJS
Copy link
Contributor

Have you read the Contributing Guidelines on Pull Requests?

Yes

Description

Created a GitHub spell checking action

Checklist

  • I've read the contribution guidelines.
  • I've checked the issue list before deciding what to submit.
  • I've edited the README.md and link to my code.

Related Issues or Pull Requests

Closes: #5

@vercel
Copy link

vercel bot commented Apr 7, 2021

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/neoalgo-docs/neo-algo-docs/BFWzMjmnQtg96rjtLLvUP9k1zpxX
✅ Preview: https://neo-algo-docs-git-fork-tidbitsjs-spellcheckgh-neoalgo-docs.vercel.app

@TidbitsJS
Copy link
Contributor Author

Let me know whether this is the right one or not @HarshCasper :)

Copy link
Contributor

@vybhav72954 vybhav72954 left a comment

Choose a reason for hiding this comment

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

Thanks for contributing to NeoAlgo.

I have suggested a few changes, kindly get them done!!!

@@ -0,0 +1,15 @@
name: Spellcheck Action
on: push
Copy link
Contributor

Choose a reason for hiding this comment

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

Hey @TidbitsJS first of all the action should be triggered on both push and pull requests, kindly make the required changes.

Use master for branch flag.

- uses: rojopolis/spellcheck-github-actions@0.11.0
name: Spellcheck
with:
source_files: "**/*.md"
Copy link
Contributor

Choose a reason for hiding this comment

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

I see you have added the source_files tab, but one important thing is missing.

See this issue I opened in the Repo, I have posted a solution I found as well along with other available solutions (which are better).

Kindly incorporate them in your action as well.

The thing is as of now this action will create a lot of noise because it will check each and every md file in the codebase whenever a file is pushed/pull request made. Obviously, we don't want that. The solution for the problems can be found in the thread I mentioned above.

Please try to integrate them here as well.

@@ -0,0 +1,16 @@
Docusaurus
Copy link
Contributor

Choose a reason for hiding this comment

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

In case you find it helpful, this is my wordlist, try adding a few words as per your understanding in your wordlist.

@TidbitsJS
Copy link
Contributor Author

@vybhav72954, I have made the changes.
Let me know whether it is correct or not :)

@vybhav72954
Copy link
Contributor

@TidbitsJS I think the additions are good, but can you please test this action once as well?

@TidbitsJS
Copy link
Contributor Author

@TidbitsJS I think the additions are good, but can you please test this action once as well?

I actually have tested this on push. But I think, it's working as usual ( like the previous one ).
I will be needing your help with that.

@vybhav72954
Copy link
Contributor

We can do two things, either I can run a few tests locally on my system. or we can do it on a separate branch in your fork.

@TidbitsJS
Copy link
Contributor Author

We can do two things, either I can run a few tests locally on my system. or we can do it on a separate branch in your fork.

Okay.
How about both of us testing that out? 😄
I will create a separate branch in my fork & will share the result.

@TidbitsJS
Copy link
Contributor Author

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.

Is this the expected behavior?

@vybhav72954
Copy link
Contributor

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.

Is this the expected behavior?

Yup, that's the problem actually with the action used. It works on the whole codebase, no mater what (if I am actually understanding what you are saying 😛)

Can you tell me which branch you are using for testing, I think I need to take a closer look as am getting a bit confused.

@TidbitsJS
Copy link
Contributor Author

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.
Is this the expected behavior?

Yup, that's the problem actually with the action used. It works on the whole codebase, no mater what (if I am actually understanding what you are saying )

Can you tell me which branch you are using for testing, I think I need to take a closer look as am getting a bit confused.

You got me 😅
Yeah, here is the pull request where I checked the test - link, branch name - testSpellCheck ( There is another branch as well, named spellCheck, which I was trying previously )

@vybhav72954
Copy link
Contributor

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.
Is this the expected behavior?

Yup, that's the problem actually with the action used. It works on the whole codebase, no mater what (if I am actually understanding what you are saying )

Can you tell me which branch you are using for testing, I think I need to take a closer look as am getting a bit confused.

You got me 😅
Yeah, here is the pull request where I checked the test - link, branch name - testSpellCheck ( There is another branch as well, named spellCheck, which I was trying previously )

Great you have performed enough tests here. Let me see how i can help

@TidbitsJS
Copy link
Contributor Author

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.
Is this the expected behavior?

Yup, that's the problem actually with the action used. It works on the whole codebase, no mater what (if I am actually understanding what you are saying )
Can you tell me which branch you are using for testing, I think I need to take a closer look as am getting a bit confused.

You got me sweat_smile
Yeah, here is the pull request where I checked the test - link, branch name - testSpellCheck ( There is another branch as well, named spellCheck, which I was trying previously )

Great you have performed enough tests here. Let me see how i can help

Yes, waiting for your solution :)

@vybhav72954
Copy link
Contributor

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.
Is this the expected behavior?

Yup, that's the problem actually with the action used. It works on the whole codebase, no mater what (if I am actually understanding what you are saying )
Can you tell me which branch you are using for testing, I think I need to take a closer look as am getting a bit confused.

You got me sweat_smile
Yeah, here is the pull request where I checked the test - link, branch name - testSpellCheck ( There is another branch as well, named spellCheck, which I was trying previously )

Great you have performed enough tests here. Let me see how i can help

Yes, waiting for your solution :)

Hey @TidbitsJS
Can you have a look at this action

Spell-Checker is taking a bit too much time. Here is an instance where I was able to identify the Files changes in PR but there is still a bit too much noise.

@TidbitsJS
Copy link
Contributor Author

@vybhav72954, I tested it on a pull request from a test to the main branch.
At the start, it's showing all the possible misspelled words.
& when I push changes ( wrong words ), then it's showing the previous misspelled words ( which I left as it is, without correcting ) + new ones.
If I remove any other word from wordList then the action is showing that misspelled word on the next push as well.
Is this the expected behavior?

Yup, that's the problem actually with the action used. It works on the whole codebase, no mater what (if I am actually understanding what you are saying )
Can you tell me which branch you are using for testing, I think I need to take a closer look as am getting a bit confused.

You got me sweat_smile
Yeah, here is the pull request where I checked the test - link, branch name - testSpellCheck ( There is another branch as well, named spellCheck, which I was trying previously )

Great you have performed enough tests here. Let me see how i can help

Yes, waiting for your solution :)

Hey @TidbitsJS
Can you have a look at this action

Spell-Checker is taking a bit too much time. Here is an instance where I was able to identify the Files changes in PR but there is still a bit too much noise.

Okay. I'll go through it & will make changes accordingly.

Thank you for helping me :)

@vybhav72954
Copy link
Contributor

@TidbitsJS Hey man, any luck with the action?

Copy link
Contributor

@ankitaggarwal23 ankitaggarwal23 left a comment

Choose a reason for hiding this comment

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

Closing this due to inactivity since last 21 days. Thank you for your valuable time.😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add a GH Action for checking spellings
4 participants