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

Docs: Fixed Typo #14007

Merged
merged 1 commit into from Jan 18, 2021
Merged

Docs: Fixed Typo #14007

merged 1 commit into from Jan 18, 2021

Conversation

@Yash-Singh1
Copy link
Contributor

@Yash-Singh1 Yash-Singh1 commented Jan 15, 2021

No description provided.

@eslint-deprecated
Copy link
Contributor

@eslint-deprecated eslint-deprecated bot commented Jan 15, 2021

Hi @Yash-Singh1!, 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 must be one of the following:

    The Tag is one of the following:

    • Fix - for a bug fix.
    • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
    • New - implements a new feature.
    • Breaking - for a backwards-incompatible enhancement or feature.
    • Docs - changes to documentation only.
    • Build - changes to build process only.
    • Upgrade - for a dependency upgrade.
    • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

    You can use the labels of the issue you are working on to determine the best tag.

  • There should be a space following the initial tag and colon, for example 'New: Message'.

Read more about contributing to ESLint here

@Yash-Singh1 Yash-Singh1 changed the title Itm -> Item Docs: Fixed Typo in Docs Jan 15, 2021
@eslint-deprecated
Copy link
Contributor

@eslint-deprecated eslint-deprecated bot commented Jan 15, 2021

Hi @Yash-Singh1!, 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 must be one of the following:

    The Tag is one of the following:

    • Fix - for a bug fix.
    • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
    • New - implements a new feature.
    • Breaking - for a backwards-incompatible enhancement or feature.
    • Docs - changes to documentation only.
    • Build - changes to build process only.
    • Upgrade - for a dependency upgrade.
    • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

    You can use the labels of the issue you are working on to determine the best tag.

  • There should be a space following the initial tag and colon, for example 'New: Message'.

Read more about contributing to ESLint here

@Yash-Singh1 Yash-Singh1 changed the title Docs: Fixed Typo in Docs Docs: Fixed Typo Jan 15, 2021
@eslint-deprecated
Copy link
Contributor

@eslint-deprecated eslint-deprecated bot commented Jan 15, 2021

Hi @Yash-Singh1!, 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 must be one of the following:

    The Tag is one of the following:

    • Fix - for a bug fix.
    • Update - either for a backwards-compatible enhancement or for a rule change that adds reported problems.
    • New - implements a new feature.
    • Breaking - for a backwards-incompatible enhancement or feature.
    • Docs - changes to documentation only.
    • Build - changes to build process only.
    • Upgrade - for a dependency upgrade.
    • Chore - for anything that isn't user-facing (for example, refactoring, adding tests, etc.).

    You can use the labels of the issue you are working on to determine the best tag.

  • There should be a space following the initial tag and colon, for example 'New: Message'.

Read more about contributing to ESLint here

@mdjermanovic
Copy link
Member

@mdjermanovic mdjermanovic commented Jan 18, 2021

LGTM, thanks! The change makes sense to me.

In the future, please be sure to fill out the pull request template. Thanks!

@mdjermanovic mdjermanovic merged commit a4fdb70 into eslint:master Jan 18, 2021
13 checks passed
@eslint-github-bot eslint-github-bot bot locked and limited conversation to collaborators Jul 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

2 participants