You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Otavio Rodolfo Piske (Jira)" <ji...@apache.org> on 2022/10/26 15:54:00 UTC
[jira] [Assigned] (CAMEL-18656) Camel-git always merge at master branch
[ https://issues.apache.org/jira/browse/CAMEL-18656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Otavio Rodolfo Piske reassigned CAMEL-18656:
--------------------------------------------
Assignee: Otavio Rodolfo Piske
> Camel-git always merge at master branch
> ---------------------------------------
>
> Key: CAMEL-18656
> URL: https://issues.apache.org/jira/browse/CAMEL-18656
> Project: Camel
> Issue Type: Bug
> Components: camel-git
> Affects Versions: 3.18.3, 3.19.0
> Reporter: Gilvan Filho
> Assignee: Otavio Rodolfo Piske
> Priority: Major
>
> [Merge operations|[https://github.com/apache/camel/blob/main/components/camel-git/src/main/java/org/apache/camel/component/git/producer/GitProducer.java#L511]] always is done at _master_ branch.
> Once default branch name can be whatever user needs and _master_ is being replaced by _main_ in many repo this could led to problems. That way camel-git needs to allow user especify a targetBranch and, if this are no set, get default branch from user configs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)