Skip to content

Conversation

josecelano
Copy link
Member

@josecelano josecelano commented Apr 13, 2022

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.

fixes #119

@josecelano josecelano force-pushed the issue-123-stop-using-short-commit-hashes branch from 04c9458 to ff01187 Compare April 13, 2022 16:04
@github-actions
Copy link

github-actions bot commented Apr 13, 2022

MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 5 0 0.15s
✅ COPYPASTE jscpd yes no 1.49s
✅ CREDENTIALS secretlint yes no 0.8s
✅ GIT git_diff yes no 0.01s
✅ JAVASCRIPT standard 1 0 0 1.17s
✅ JSON eslint-plugin-jsonc 7 0 0 0.81s
✅ JSON jsonlint 7 0 1.61s
✅ JSON prettier 7 0 0 0.53s
✅ JSON v8r 7 0 6.11s
✅ MARKDOWN markdownlint 2 0 0 0.32s
✅ MARKDOWN markdown-link-check 2 0 3.32s
✅ MARKDOWN markdown-table-formatter 2 0 0 0.25s
✅ SPELL cspell 79 0 3.08s
✅ SPELL misspell 79 0 0 0.16s
✅ TYPESCRIPT eslint 52 0 0 11.26s
✅ YAML prettier 8 0 0 0.76s
✅ YAML v8r 8 0 8.23s
✅ YAML yamllint 8 0 0.28s

See errors details in artifact MegaLinter reports on CI Job page

@josecelano
Copy link
Member Author

josecelano commented Apr 13, 2022

@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.

@da2ce7
Copy link
Contributor

da2ce7 commented Apr 13, 2022

@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.

@da2ce7 da2ce7 force-pushed the issue-123-stop-using-short-commit-hashes branch from ff01187 to ea85e15 Compare April 13, 2022 17:45
@da2ce7
Copy link
Contributor

da2ce7 commented Apr 13, 2022

@josecelano rebased.

@da2ce7 da2ce7 changed the title Use only full commit hashes Issue #123: Use Full SHA1 Commit Hashes Apr 13, 2022
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.
@josecelano josecelano force-pushed the issue-123-stop-using-short-commit-hashes branch from ea85e15 to ec1d939 Compare April 18, 2022 10:35
Copy link
Collaborator

@yeraydavidrodriguez yeraydavidrodriguez left a comment

Choose a reason for hiding this comment

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

Looks good

@josecelano josecelano merged commit a22c90a into main Apr 18, 2022
@josecelano josecelano deleted the issue-123-stop-using-short-commit-hashes branch April 18, 2022 11:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stop using short commit hashes Action output inconsistency
3 participants