-
Notifications
You must be signed in to change notification settings - Fork 67
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
Task fails with error "--local can only be used inside a git repository" #25
Comments
@fabian-schwarz i don't see the reason for configuring the base directory for git, it should be always "System.DefaultWorkingDirectory" |
@mlarhrouch you can checkout multiple repositories in Azure Pipelines, thus it is not always "System.DefaultWorkingDirectory" |
@fabian-schwarz in this case maybe using "Build.Repository.LocalPath" instead of "System.DefaultWorkingDirectory" is the best solution ? https://learn.microsoft.com/en-us/azure/devops/pipelines/build/variables?view=azure-devops&tabs=yaml |
@mlarhrouch think this would only do half the job, it would only help if the repo we want to use is the "self" repo, another we can't reach with this variable. Still would love to have the option to define my custom working dir to target any checked out repo, which can default to either "System.DefaultWorkingDirectory" or "Build.Repository.LocalPath". |
we need this fix, i always pull multiple git repos in my pipelines, for multiple reason. i don't want to do a job just for that... i need the fix of that he can use the multiple directory path |
I am using Microsoft hosted agents and checkout put the code into System.DefaultWorkingDirectory / so basePath configuration is needed. |
The tasks errors out in my pipeline with the error message :
##[error]fatal: --local can only be used inside a git repository
Maybe due to the pipeline checking out more than one repository:
Probably fixed by making the following line configurable:
azure-pipeline-gpt-pr-review/GPTPullRequestReview/src/git.ts
Line 7 in 1db7cfa
The text was updated successfully, but these errors were encountered: