[ 
https://issues.apache.org/jira/browse/SCM-875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17963436#comment-17963436
 ] 

ASF GitHub Bot commented on SCM-875:
------------------------------------

jira-importer commented on issue #1099:
URL: https://github.com/apache/maven-scm/issues/1099#issuecomment-2964645803

   **[Michael 
Osipov](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=michael-o)**
 commented
   
   Fixed with 
[e81778d63cfd6cff7a5fa5a14644440b758e35f2](https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=e81778d63cfd6cff7a5fa5a14644440b758e35f2).
   




> GitUpdateCommand assumes master branch by default
> -------------------------------------------------
>
>                 Key: SCM-875
>                 URL: https://issues.apache.org/jira/browse/SCM-875
>             Project: Maven SCM (Moved to GitHub Issues)
>          Issue Type: Bug
>          Components: maven-scm-provider-gitexe
>    Affects Versions: 1.9.5
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>            Priority: Major
>             Fix For: 1.10.0
>
>
> The {{GitUpdateCommand}} and its user {{scm:update}} always assume that we 
> are locally on {{master}} and it can be used for {{log}}, {{pull}}, etc.
> It shouldn't assume any branch, but rely on what {{HEAD}} is pointing to.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to