Skip to content

Respecting the optional scope in Conventional Commits

Open

Description

The Pull Request section of the ESLint documentation explicitly mentions that

All ESLint projects follow Conventional Commits for our commit messages1.

The convention for Conventional Commits is

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

However, ESLint Bot doesn't recognize the scope part of the commit message, so contributors who are already used to Conventional Commits have to modify the commit message to remove the scope part and recommit.

This caused some trouble. ESLint uses, but not exclusively, Conventional Commits

Footnotes

  1. Pull Requests - ESLint - Pluggable JavaScript Linter

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

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    • Status

      Blocked

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions