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

Addiing gh action for spelling errors #1174

Merged
merged 12 commits into from
Jul 4, 2023
Merged

Addiing gh action for spelling errors #1174

merged 12 commits into from
Jul 4, 2023

Conversation

CBID2
Copy link
Collaborator

@CBID2 CBID2 commented Jun 27, 2023

Fixes Issue

Closes #1080

Changes proposed

I added a GitHub Action that encourages contributors to revise spelling errors in their PRs.

Screenshots

github action

Note to reviewers

@saikiranreddy201, I'm open to your suggestions on how to improve this. For context, check out the GH Actions link here

@vercel
Copy link

vercel bot commented Jun 27, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
linkshub ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 2, 2023 6:17am

@CBID2 CBID2 self-assigned this Jun 27, 2023
Copy link

@github-actions github-actions bot 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, CBID2, for creating this pull request and contributing to LinksHub! 💗

The maintainers will review this Pull Request and provide feedback as soon as possible! 😇
We appreciate your patience and contribution, Keep up the great work! 😀

@CBID2 CBID2 added goal: new-feature New feature or request collab Open to collaborate with another contributor and/or maintainer labels Jun 27, 2023
@saikiranreddy201
Copy link
Contributor

Hey @CBID2, Since the "pull_request_target" event already covers "opened," "reopened," and "synchronize" types, there is no need to specify them individually.

You can achieve this by changing the follow code snippet

pull_request_target:
    branches:
    - "**"
    tags-ignore:
    - "**"
    types:
    - 'opened'
    - 'reopened'
    - 'synchronize'

to this

pull_request_target:
branches:
 - "**"
tags-ignore:
 - "**"

@CBID2
Copy link
Collaborator Author

CBID2 commented Jun 27, 2023

pull_request_target:
branches:

  • "**"
    tags-ignore:
  • "**"

Where should I put it @saikiranreddy201?

@saikiranreddy201
Copy link
Contributor

@CBID2, I have added a comment in the review section, please do checkout!

…or-spelling-errors' into addiing-gh-action-for-spelling-errors
@CBID2
Copy link
Collaborator Author

CBID2 commented Jun 27, 2023

Hey @CBID2, Since the "pull_request_target" event already covers "opened," "reopened," and "synchronize" types, there is no need to specify them individually.

You can achieve this by changing the follow code snippet

pull_request_target:
    branches:
    - "**"
    tags-ignore:
    - "**"
    types:
    - 'opened'
    - 'reopened'
    - 'synchronize'

to this

pull_request_target:
branches:
 - "**"
tags-ignore:
 - "**"

Thanks

@ujjawaltyagii
Copy link
Contributor

@CBID2 The deployment shouldn't have caused error then why deployment is getting failed 0_0

@CBID2
Copy link
Collaborator Author

CBID2 commented Jun 29, 2023

@CBID2 The deployment shouldn't have caused error then why deployment is getting failed 0_0

I don't know @ujjawaltyagii. Unfortunately, only @rupali-codes has access to Vercel.

@rupali-codes
Copy link
Owner

@CBID2 your vercel deployment is getting failed because of the following issues

image

@CBID2
Copy link
Collaborator Author

CBID2 commented Jun 29, 2023

@CBID2 your vercel deployment is getting failed because of the following issues

image

Ahh I see @rupali-code. Where should I put the file then?

@CBID2
Copy link
Collaborator Author

CBID2 commented Jun 30, 2023

@k-deepak04, I could use help with this

@k-deepak04
Copy link
Contributor

@k-deepak04, I could use help with this

Didn't get what you have written
Do you want my help in this?

@CBID2
Copy link
Collaborator Author

CBID2 commented Jul 1, 2023

@CBID2 don't know why the return does not have any code in preview , while writing that i was able to see the code.

please let me know how i can share the code.....with you

My preference is Feedback Technique # 5

@k-deepak04
Copy link
Contributor

@CBID2 tried but the deployement is still failing

@rupali-codes please give me the response ss why it's failing

@rupali-codes
Copy link
Owner

@k-deepak04 & @CBID2 its failing because of this

image

@CBID2
Copy link
Collaborator Author

CBID2 commented Jul 1, 2023

@k-deepak04 & @CBID2 its failing because of this

image

So what should I do @rupali-codes? I'm not familiar with Typescript

@k-deepak04
Copy link
Contributor

@k-deepak04 & @CBID2 its failing because of this
image

So what should I do @rupali-codes? I'm not familiar with Typescript

same have experience in nextjs,reactjs not this.

@rupali-codes
Copy link
Owner

@CBID2 & @k-deepak04 there you go!

Copy link
Collaborator Author

@CBID2 CBID2 left a comment

Choose a reason for hiding this comment

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

Done

@CBID2
Copy link
Collaborator Author

CBID2 commented Jul 2, 2023

@CBID2 & @k-deepak04 there you go!

Thank you @rupali-codes! Now I just need an approved review

@CBID2 CBID2 added the status: ready-to-merge Approved & its ready-to-merge label Jul 3, 2023
Copy link
Owner

@rupali-codes rupali-codes left a comment

Choose a reason for hiding this comment

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

@CBID2 you have tested this right?

@CBID2
Copy link
Collaborator Author

CBID2 commented Jul 3, 2023

@CBID2 you have tested this right?

No @rupali-codes. How can I go about doing so?

@rupali-codes
Copy link
Owner

@CBID2 you have tested this right?

No @rupali-codes. How can I go about doing so?

I guess we should merge and lets see :)

@CBID2
Copy link
Collaborator Author

CBID2 commented Jul 4, 2023

@CBID2 you have tested this right?

No @rupali-codes. How can I go about doing so?

I guess we should merge and lets see :)

Ok, approve my PR

@rupali-codes rupali-codes merged commit bb7aa7b into rupali-codes:main Jul 4, 2023
4 checks passed
rupali-codes added a commit that referenced this pull request Jul 5, 2023
rupali-codes added a commit that referenced this pull request Jul 5, 2023
@k-deepak04
Copy link
Contributor

image

i have tested one spell checker

@k-deepak04
Copy link
Contributor

image

i have tested one spell checker

@CBID2 check this, it detects requres spelling and other ones

@CBID2
Copy link
Collaborator Author

CBID2 commented Aug 4, 2023

image

i have tested one spell checker

@CBID2 check this, it detects requres spelling and other ones

Ok

@k-deepak04 k-deepak04 mentioned this pull request Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
collab Open to collaborate with another contributor and/or maintainer goal: new-feature New feature or request status: ready-to-merge Approved & its ready-to-merge
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature] GitHub Action to catch spelling errors
6 participants