Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am working on a project that requires me to build multiple QDI projects that are versioned in GitHub.
At this point I have created two projects, let's call them "Project A" and "Project B". Upon initializing both projects I can connect and commit the projects to separate GitHub repositories ("repo A" and "repo B") and push the initial JSON objects to the "main" branch of the corresponding repos.
**NOTE: Both of these projects are blank and have no tasks created, just the project settings modified
After commit the initial projects to their repos, I then attempted to create feature branches in either repository first with Project/Repo A (both named "mvp-development"). The new branch was successfully created in both Project A and Repo A however, when attempting to create a branch by the same name in Project B and Repo B I get the following error:
Now upon checking to see if this branch exists in Repo B I can see in GitHub that there is no branch of this name present in the repository. I also pulled the branch down to my local machine and inspected the remote branches that are reachable and can not see a branch by this name present in Repo B.
Now I can in fact create another branch of a different name in Project/Repo B therefore, this is not a permissions issue (as far as I can tell). Additionally, I have admin rights on both repositories and the Qlik Talend Cloud tenant. I have a suspicion that this is actually a bug in QDI that does not allow different projects pointing to different repos to belong to a branch of the same name regardless of being pushed to completely different GitHub repositories.
I did not find any mention of this limitation in the help docs for the QDI GitHub integration therefore, I do believe that this is a bug or intended functionality that is not currently documented as a limitation.
Please let me know if I am utilizing this feature incorrectly.
