CI: Specify safe.directory for Arm64 #309
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Beginning with version 2.35.3 of Git, it is now possible to turn off safe directory checks. This change eliminates the "unsafe repository" error messages. The update resolves unintentional errors that occurred while using git in an emulated Arm64 environment. It appears that this update is connected to a vulnerability announced: https://github.blog/2022-04-12-git-security-vulnerability-announced/
vestata
pushed a commit
to vestata/rv32emu
that referenced
this pull request
Jan 24, 2025
CI: Specify safe.directory for Arm64
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Beginning with version 2.35.3 of Git, it is now possible to turn off safe directory checks. This change eliminates the "unsafe repository" error messages. The update resolves unintentional errors that occurred while using git in an emulated Arm64 environment.
It appears that this update is connected to a vulnerability announced: https://github.blog/2022-04-12-git-security-vulnerability-announced/