Header Ads Widget

Can GitHub desktop work with GitLab?

GitHub Work area is a quick and simple method for adding to projects from Windows and operating system X, whether you are a carefully prepared client or a new client, GitHub Work area is intended to improve all cycles and work processes in your GitHub. GitHub Work area is an open-source Electron-based GitHub application. It is written in TypeScript and utilizations Respond.

It has numerous marvelous elements:

1. Crediting commits with associates without any problem

2. Checkout branches with pull demands and view CI situations with

3. Language structure featured diffs

4. Extended picture diff support

5. Broad supervisor and shell mixes

6. It's open-source

I for one like to involve the Github Work area as my principal git client as opposed to Source Tree or Gitkraken.

Last week, my employer, chose to move its codebase from Github to Gitlab. The explanation is that Gitlab has some the container Elements like coordinated DevOps inbuilt into their framework, dissimilar to Github where you'll need to do every one of these yourselves.

Pre-GitLab we were utilizing 5 distinct apparatuses and the intricacy of coordinating them everything was going crazy and very costly, attempting to integrate New Artifact, Codeship, Github, Jenkins, Gourmet expert, and Terraform was unpleasant… also Computerized Sea, AWS, Purplish blue, and MongoDB Cloud

I'm utilized to the GitHub climate since that is all I've generally worked with however I considered this to be a test to adjust to another climate.

I was prepared to move to Gitlab however I wasn't prepared to leave the GitHub Work area, so I chose to utilize Gitlab and GitHub Work area. I started making research on the most proficient method to utilize them both.

So I'll tell you the best way to utilize the GitHub Work area with a Gitlab Repo that has 2FA(two-factor validation) empowered.

So how about we visit the means without any preparation.

Stage one:

I. Download the GitHub Work are here

ii. Go to your Gitlab repo

iii. Click on settings


Stage two:

What we'll do now is create an entrance token for our GitHub work area.

In the wake of tapping on the settings

I. Click on Access Tokens

ii. Create an entrance token

iii. Duplicate your new access token and store it someplace as we'll utilize it later:


Stage three:

I. Go to your archive and select HTTPS and duplicate the connection,


ii. open the GitHub Work area from the record bar, select clone archive


iii. After choosing it, a modular would spring up, select the URL and spot the HTTPS interface we replicated from GitLab inside the URL field and select the objective envelope.


iv. In the wake of filling that large number of fields, select clone


v. While cloning, it would spring up a modular named confirmation fizzled, you would then be expected to place in your username and secret key.


N/B: Your username is generally your email address or whatever username you used to get to your GitLab association or repo.


vi. Then, at that point, your secret phrase would be the individual access token we made previously, so go to any place you might have put away it and glue it.


vii. After that click login or validate and assuming all goes well you ought to see something like this


From that point onward, you would see this


Then you can get from the beginning, consider all branches and use it to be your favored git client.


What's more, that is the way to utilize Gitlab with GitHub Work area.


If you have any inquiries or you see no steps go ahead and connect with me on Twitter or drop your inquiries in the remarks segment.


Much appreciated!!!

Reference URL

Post a Comment