The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting GitHub and GitLab to the same cloud instance

Majken Longlade
Contributor
April 24, 2023

Anyone running with both the GitHub connector and another Git repository connector like GitLab to populate the development panel?

Wondering if they cause any conflicts with each other. 

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Andre Dias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 25, 2023

Hi Majken!

 

In a nutshell: yes, you can both! Jira has no restriction on how many code tools you have linked to your site or even to a single issue - it's not exclusive to one or the other. If you mention the same issue key in GitHub, Bitbucket, and GitLab, they will all appear in their dedicated section of the development panel. Still, the sum of each category (branches, commits, PRs, builds, deployments) will be displayed in the development panel without specifying how many come from each source. As can be seen in the screenshots below from my test site, I've connected all three of them and two Bitbucket workspaces, and both have a separate section:

 

screenshot-3.pngscreenshot-1.png

 

This setup won't cause any glitches or errors, the only thing to keep in mind is that having both GitLab and GitHub pointing to the same issue could cause some confusion from a process point of view, but if you're okay with this approach - go for it!

DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events