![setting up repository smartgit setting up repository smartgit](https://benisnous.com/wp-content/uploads/2021/06/How-To-Fix-Error-Setting-Up-Base-Repository.jpg)
All changes for Project 1, Project 2, and the Sub-Project are tracked on their own repositories. The core concept is pretty simple: you can have smaller Git repos, with their upstream linked to a sub-repository, but embedded in another project. For this, Git Subtree provides a solution. However, there are many cases where you’d want the best of both worlds-maintaining it centrally as a package, but also allowing direct embedding and editing in multiple projects. In Visual Studio, this can be done easily with Project References.
SETTING UP REPOSITORY SMARTGIT CODE
This solves the problem, because if you modify code in the subproject, it will be updated whenever you re-build. This isn’t as crazy as you might think, and works well if all your code is in the same domain Google uses a monorepo for all their code, and Microsoft u ses one for all. The other solution is to use a monorepo, one giant repository for all your code. It also introduces complications for local development. However, if you’re changing this code on a regular basis, having to integrate, publish, and pull new versions of the project from a third party source simply does not work as well as having the code directly accessible. This works very well for things that are not updated or maintained often, and can afford to be distributed to their consumers in discreet version numbers. =, the most obvious solution is to make the subproject into a package, and distribute it on a package manager like NPM or NuGet. Add following lines to smartgit.properties (in SmartGit’s settings directory):
![setting up repository smartgit setting up repository smartgit](https://intland.com/wp-content/uploads/2014/09/how_to_setting_up_git_repositories_featured_image.jpg)
Now SmartGit has to be configured to authenticate with this custom application. Next, Azure DevOps will display the application details. This is what the user has to copy over to SmartGit’s Generate Token dialog.įinally, confirm with Create Application. The code will be passed as URL parameter code. Once SmartGit initiates the OAuth authentication, Azure DevOps will return the initial code to the Authorization callback URL. Then configure the application, with your custom Authorization callback URL and scopes Code (read and write) selected. Azure DevOps configurationįirst, you have to create the application in your Azure DevOps profile. To get OAuth authentication working for Azure DevOps On-Premise instances or to avoid callbacks to you can set up a custom Azure DevOps application and configure SmartGit to use it for OAuth authentication. Setting up a custom Azure DevOps Application for SmartGit
SETTING UP REPOSITORY SMARTGIT PASSWORD
When SmartGit asks you for User Name and Password enter these credentials. If you are just interested in accessing your Azure DevOps Git repositories, but you don’t need the additional Azure DevOps Hosting Provider functionality (like managing pull requests in SmartGit), you may open the Azure website, navigate to your Azure DevOps repository, invoke Clone and then Generate Git Credentials. Repository access using “Generate Git Credentials” Organization access is set to All accessible organizations (even if For PATs to be usable by SmartGit, it’s important that PersonalĪccess tokens can be generated in the Settings area of the Azure web If OAuth is no feasible option for you, the Azure DevOps integration canĪlternatively be set up using a personal access token (“PAT”). Alternative setup using a personal access token This requires to login forĮvery account in your web browser before invoking Generate API If you have multiple Azure DevOps accounts, you can run through theĪbove procedure for each of your accounts. If above procedure fails make sure to allow Third-party applicationĪccess via OAuth in your Organization Settings. it will not require to create/enter a second set of credentials to SmartGitįinally, confirm the Add Hosting Provider dialog using Add.its scope is more limited than plain password or possibly more powerful personal access tokens.Using the OAuth-token has following advantages: This will return the generated OAuth-token when Git asks for credentials (username + password) when connecting to your GitHub repository. The code will be used to create an applicationĪccess token which will be used to populate the Token field.īy default, Use OAuth token for repository authentication will be selected. , where the generated access code will be displayed.Ĭopy&paste this code into SmartGit’s Generate API Token dialog and
![setting up repository smartgit setting up repository smartgit](https://www.attosol.com/content/images/2018/12/smartgit_log_view.png)
Once you have confirmed this page, you will be redirected to This should open up your default web browser where you will Provider dialog, have Azure DevOps selected and invoke GenerateĪPI token.
![setting up repository smartgit setting up repository smartgit](https://i.stack.imgur.com/l0jSj.png)
To set up the Azure DevOps integration, go to Preferences, section Some behavior can be customized by system properties. SmartGit integrates Azure DevOps workflows in various places, very