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

chore: Fixed Typo in CLI Engine #15497

Merged
merged 1 commit into from Jan 8, 2022

Conversation

akgupta0777
Copy link
Contributor

@akgupta0777 akgupta0777 commented Jan 7, 2022

Prerequisites checklist

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core

  • Other, please explain: Simple Typo Fix

What changes did you make? (Give an overview)

Just a simple typo fix in the comments.

Is there anything you'd like reviewers to focus on?

nope

@eslint-github-bot eslint-github-bot bot added the triage label Jan 7, 2022
@eslint-github-bot
Copy link

eslint-github-bot bot commented Jan 7, 2022

Hi @akgupta0777!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

  • The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
  • There should be a space following the initial tag and colon, for example 'feat: Message'.
  • The first letter of the tag should be in lowercase

To Fix: You can fix this problem by running git commit --amend, editing your commit message, and then running git push -f to update this pull request.

Read more about contributing to ESLint here

@akgupta0777 akgupta0777 changed the title Fixed Typo in CLI Engine fix: Fixed Typo in CLI Engine Jan 7, 2022
@eslint-github-bot
Copy link

eslint-github-bot bot commented Jan 7, 2022

Hi @akgupta0777!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

  • The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
  • There should be a space following the initial tag and colon, for example 'feat: Message'.
  • The first letter of the tag should be in lowercase

To Fix: You can fix this problem by running git commit --amend, editing your commit message, and then running git push -f to update this pull request.

Read more about contributing to ESLint here

@akgupta0777 akgupta0777 changed the title fix: Fixed Typo in CLI Engine chore: Fixed Typo in CLI Engine Jan 7, 2022
@eslint-github-bot
Copy link

eslint-github-bot bot commented Jan 7, 2022

Hi @akgupta0777!, thanks for the Pull Request

The first commit message isn't properly formatted. We ask that you update the message to match this format, as we use it to generate changelogs and automate releases.

  • The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
  • There should be a space following the initial tag and colon, for example 'feat: Message'.
  • The first letter of the tag should be in lowercase

To Fix: You can fix this problem by running git commit --amend, editing your commit message, and then running git push -f to update this pull request.

Read more about contributing to ESLint here

@eslint-github-bot eslint-github-bot bot added the chore label Jan 8, 2022
@mdjermanovic mdjermanovic added accepted and removed triage labels Jan 8, 2022
Copy link
Member

@mdjermanovic mdjermanovic left a comment

LGTM, thanks for contributing!

Copy link
Contributor

@snitin315 snitin315 left a comment

LGTM

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
accepted archived due to age chore
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants