Skip to content
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

Run "git log" under the same user that cloned the repo #165

Merged
merged 1 commit into from
Nov 5, 2023

Conversation

sleinen
Copy link
Contributor

@sleinen sleinen commented Nov 5, 2023

This avoids "fatal: detected dubious ownership in repository" errors that cause all feature-detection commands to fail.

Fixes #164

Copy link
Owner

@lae lae left a comment

Choose a reason for hiding this comment

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

Instead of adding the become parameters to each task, can you move the check tasks into their own block and use the become parameters on the block itself? (This does mean indenting all of the check tasks.)

(also just in case: please force push an amended commit to this branch rather than creating a new PR/new commit.)

This avoids "fatal: detected dubious ownership in repository" errors
that cause all feature-detection commands to fail.
@lae lae merged commit 69119aa into lae:master Nov 5, 2023
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.

Git-based installation: problematic file ownership
2 participants