Commit hashes are not ignored
See original GitHub issueExpected Behavior
Hello, anyway I can ignore a commit hash Is the above possible with commitlinjs
Current Behavior
module.exports = {
// More about these rules https://commitlint.js.org/#/reference-rules
rules: {
"ignores": [
(commit) => commit === '664b8f72b90c4686c513042bcd72666418953f09',
],
};
Commit hashes are still not ignored.
Affected packages
- cli
- core
- prompt
- config-angular
Possible Solution
Commit hash should be ignored
Steps to Reproduce (for bugs)
- First step
- Second step
commitlint.config.js
```js ```Context
Your Environment
Executable | Version |
---|---|
commitlint --version |
VERSION |
git --version |
VERSION |
node --version |
VERSION |
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10
Top Results From Across the Web
get the git commit hash of the last commit which affected files ...
The following script will go backwards through the revision history and find the first commit to have a change that would not be...
Read more >npm ci is ignoring commit hash - package is not updated #980
Essentially it is ignoring the commit hash. npm ci should understand when the commit hash has changed in the package.json and download the ......
Read more >Ignoring mass reformatting commits with git blame
Each commit has to be the full 40 character hash and we're allowed comments. We can then ignore all the commits in the...
Read more >git-show Documentation - Git
If the commit is a merge, and if the pretty-format is not oneline, ... Lines starting with a hash (" # ") are...
Read more >Does git commit hash prove the history until that point?
SHA-1 (the hash used in git) is not considered cryptographically secure these ... If you ignore the possibility of SHA-1 collision attacks, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In this example project it only fetches X commits. Maybe that works for you:
https://github.com/escapedcat/rusty-cli/blob/main/.github/workflows/convco.yml#L13
It’s not commitlint in this case but might work
Thanks for the quick reply. That’s a good point. I currently had the lint running on a push-hook, which caused problems when pushing new branches (containing the old commits). It’s true that probably the simplest thing is to move this to a commit-hook. Thank you!