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.

Sign up for GitHub

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

Jump to bottom

Crash on linting the initial commit #4

Open
WGH- opened this issue Aug 12, 2020 · 2 comments
Open

Crash on linting the initial commit #4

WGH- opened this issue Aug 12, 2020 · 2 comments

Comments

@WGH-
Copy link
Contributor

WGH- commented Aug 12, 2020 •
edited
Loading 

remote: Git Burn rejected your commits.
remote:
remote: commit cb739a597f03a2f0a929b23c04e3c76910a08a05
remote: Author: WGH <[email protected]>
remote: Date:   Wed Aug 12 13:58:14 2020 +0300
remote:
remote:     Initial commit
remote:
remote: An error occurred while executing '/usr/libexec/git-core/git rev-list cb739a597f03a2f0a929b23c04e3c76910a08a05^...cb739a597f03a2f0a929b23c04e3c76910a08a05': b"fatal: ambiguous argument 'cb739a597f03a2f0a929b23c04e3c76910a08a05^...cb739a597f03a2f0a929b23c04e3c76910a08a05': unknown revision or path not in the working tree.\nUse '--' to separate paths from revisions, like this:\n'git <command> [<revision>...] -- [<file>...]'"
remote:
remote: error: hook declined to update refs/heads/master

The error is printed by gitlint.
@WGH-
Copy link
Contributor Author

WGH- commented Aug 12, 2020

https://jorisroovers.com/gitlint/ gitlint documentation suggests to use this syntax for linting a single commit, but that clearly doesn't work for the initial commit

@WGH-
Copy link
Contributor Author

WGH- commented Aug 12, 2020

jorisroovers/gitlint#141

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@WGH-