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

Forever violations even after being edited #536

Closed
5ouma opened this issue Oct 31, 2023 · 2 comments
Closed

Forever violations even after being edited #536

5ouma opened this issue Oct 31, 2023 · 2 comments

Comments

@5ouma
Copy link

5ouma commented Oct 31, 2023

Even if I edit the warned commit message via e(dit), it outputs the same warning.
I use Gitlint as gitlint --target='/path/to/repo' install-hook to set the commit-msg hook globally with hooksPath = ~/.config/git/hooks.

I think this is because it doesn't read the commit message after edited.

@sigmavirus24
Copy link
Collaborator

Duplicate of #180 potentially.

Please ensure you're on the latest version and provide more information to help debug this

@5ouma
Copy link
Author

5ouma commented Oct 31, 2023

Yes, you're right.
I used v0.19.1 the latest version for GitHub releases. If it's possible, please make a release to become able to install via Homebrew.

I'm looking forward to it being released v0.20.0 as soon as possible.
Over 7 months have passed since @jorisroovers opened #462. (I know they didn't promise though.)

@5ouma 5ouma closed this as completed Oct 31, 2023
@5ouma 5ouma closed this as not planned Won't fix, can't repro, duplicate, stale Oct 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants