-
Notifications
You must be signed in to change notification settings - Fork 3
Issue #123: Use Full SHA1 Commit Hashes #142
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
Conversation
04c9458
to
ff01187
Compare
MegaLinter status: ✅ SUCCESS
See errors details in artifact MegaLinter reports on CI Job page |
@da2ce7 in this case the dependency update is mixed up with the rest of the code in the same commit because it's a breaking change. The commit would not work if we only had a commit with the dependency update. |
@josecelano This is Correct. The minimal amount of changes to facilitate a dependency change should be included in the commit that changes the dependency. - Every commit should pass the CI. |
ff01187
to
ea85e15
Compare
@josecelano rebased. |
Bug external project: nautilus-cyberneering/library-consumer#22 Internal issue: #123 The bug was temporarily fixed by setting git config to: git config --global core.abbrev 7 We do not need it anymore becuase SimpleGit has force commit hash length to the maximum (40 chararters). So we only use full hashes.
ea85e15
to
ec1d939
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
Bug external project: nautilus-cyberneering/library-consumer#22
Internal issue: #123
The bug was temporarily fixed by setting git config to:
We do not need it anymore becuase SimpleGit has force commit hash length
to the maximum (40 chararters). So we only use full hashes.
fixes #119