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

fix: Fixed commit format verification prompt for Windows users #561

Merged
merged 6 commits into from
Oct 10, 2016
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -159,11 +159,6 @@ If you want to use scopes then it would look more like:
The commit message formatting described above is automatically enforced
each time you commit to your work branch to make continuous integration smoother.

**If you're on Windows**, the commit message verification currently doesn't
work (sorry!). You will need to commit to your branch using this command:

git commit --no-verify

## Creating a release

To release a new version of `web-ext`, follow these steps:
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@
"eslint-plugin-flowtype": "2.20.0",
"firefox-client": "0.3.0",
"flow-bin": "0.33.0",
"git-hooks": "1.1.1",
"git-hooks-win": "1.1.11",
Copy link
Contributor

@kumar303 kumar303 Oct 8, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good find! This looks really promising and it sounds like it will also work on Mac. However, since the installation of this module installs a hook script, I think we also need to remove the old git-hooks dependency, right? Otherwise both of them will be modifying the hook script.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, I didn't want to mess with the original package since I don't have a mac to try if this one works properly on Mac too. If it does we should remove the other one and keep the windows compatible ,otherwise I'll try one of the few other solutions I looked into (like grunt-git-hooks) which are a bit more complicated.

"grunt": "1.0.1",
"grunt-contrib-clean": "1.0.0",
"grunt-contrib-copy": "1.0.0",
Expand Down