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

404 in Example config link #577

Closed
1 task done
ghost opened this issue Feb 8, 2019 · 1 comment · Fixed by #578
Closed
1 task done

404 in Example config link #577

ghost opened this issue Feb 8, 2019 · 1 comment · Fixed by #578

Comments

@ghost
Copy link

ghost commented Feb 8, 2019

I got a http 404 error when you fail a commit

Expected Behavior

A working link :)

Current Behavior

The example config's link advised by the cli error message is https://git.io/fpUzm

Affected packages

  • cli

Possible Solution

Maybe redirect to this link instead

Steps to Reproduce (for bugs)

After a fresh install with husky following this guide: https://conventional-changelog.github.io/commitlint/#/./guides-local-setup?id=guides-local-setup

I tested with:

> git commit -m 'commitlint'
husky > pre-commit (node v11.6.0)
husky > commit-msg (node v11.6.0)

⧗   input: commitlint
✖   Please add rules to your `commitlint.config.js`
    - Getting started guide: https://git.io/fpUzJ
    - Example config: https://git.io/fpUzm [empty-rules]
✖   found 1 problems, 0 warnings 
    (Need help? -> https://github.com/conventional-changelog/commitlint#what-is-commitlint )

Context

Was trying to configure commitlint

Your Environment

Mac OSX Mojave 10.14.2

Executable Version
commitlint --version 7.5.0
git --version 2.17.2 (Apple Git-113)
node --version v11.6.0
@byCedric
Copy link
Member

byCedric commented Feb 9, 2019

Thanks for reporting! We have switched to the conventional changelog organization but missed this reference to the old link. I'll fix this asap.

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

Successfully merging a pull request may close this issue.

1 participant