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

Git commit message linter #75

Open
vemv opened this issue Jun 3, 2019 · 0 comments
Open

Git commit message linter #75

vemv opened this issue Jun 3, 2019 · 0 comments

Comments

@vemv
Copy link
Contributor

vemv commented Jun 3, 2019

Context

Certain commit messages can be dangerous (fixes #7 lacks a namespace, can close unreated issues if the commit is moved to a new repo) simply not that recommended.

Task

Create a linter that analyzes the git log output.

Acceptance criteria

  • The git log is only examined under certain circumstances, so that f-s doesn't pester the user about already-accepted commits.

A simple starting point would be to only add the linter to the formatting-stack.branch-formatter ns.

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

No branches or pull requests

1 participant