fix: git detected dubious ownership in repository #4002
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
…penMLDB' for some workflow actions Signed-off-by: shouren <[email protected]>
github-actions
bot
added
workflow
…n CMakeList.txt in third-party dir when envs are set. Signed-off-by: shouren <[email protected]>
Shouren
force-pushed
the
fix/git-detected-dubious-ownership-in-repository
branch
from
12b486d to
dea0567
Compare
Signed-off-by: shouren <[email protected]>
Shouren
force-pushed
the
fix/git-detected-dubious-ownership-in-repository
branch
from
a344243 to
53c89bb
Compare
Signed-off-by: shouren <[email protected]>
github-actions
bot
added
the
storage-engine
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.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
Some actions may failed by this error
What is the new behavior (if this is a feature change)?
Make those actions works