fix: prevent gpg from disrupting initial commit in addon change tracking repo #77
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
When
git config --global --get commit.gpgsignistrue(which GitHub documentation notes as an option when users want to sign all commits by default in any local repository on their computer),AddonsRepository.InstallAddonFromCache(...)fails when it attempts to rungit commit -m Initial Commit.This PR also changes the command from
git commit -m Initial Committogit commit -m "Initial Commit", but this was not the cause of the issue.Discord message link describing issue: https://discord.com/channels/862108653488963604/1020542645677867128/1279413401159860226