Server to merge the pull request and then SmartGit will pull theĬorresponding branch, so you will have the merged changes locally Required before you are willing to pull his changes. Signal the initiator of the pull request, that modifications are After commentingĬhanges, it’s probably a good idea to Reject the pull request to Which a multi-commit pull request includes and you canĬomment on these changes, if necessary. When selecting this merge node in the Commits view, you can see the entire changes This will fetch all commits from the remote repository to a specialīranch in your local repository and will create an additional, virtual mergeĬommit between the base commit from which the pull request has beenįorked and the latest (remote) pull request commit. You first have to fetch them by invoking Fetch Pull Request from the context menu of the pull request. to review their commits, or Merge or Reject them), The retrieved information in the Branches. SmartGit learns about them only by calling a GitHub REST API and displays Incoming pull requests, in first place, are just present on the server. They areĭisplay directly below the local (or if it does not exist), the Users/repositories, requesting them to pull your changes. Outgoing pull requests are those which you have sent to other.Separate category called Pull Requests in the Branches view. Requesting to pull from their repositories. Incoming pull requests are those which other users are.On related Pull Requests from the GitHub server: When initially loading the Log, SmartGit will also refresh information In the Log window of your repository, you can interact with GitHub in Noteĭetailed pull request information and operations on pull requests are Indicates incoming pull requests in the title of the Branches view. The main window contains a light-weight GitHub integration which just SmartGit will display your own ( user) repositories,Īs well as repositories of your organization ( org). When cloning a repository, you can select your repository from a list, instead ofĮntering the URL. Repo, read:org, read:user, gist, workflow Clone In this case make sure that your personal access token has at least following scopes selected: Instead of an OAuth token, you may alternatively use a personal access token which has to be created manually in GitHub’s UI. Through the Authorization process outlined above, you have to Revoke Settings, section Authorized Applications. Once you have authorized SmartGit, it will show up in your GitHub it will not require to create/enter a second set of credentials to SmartGitįinally, confirm the Add Hosting Provider dialog using Add.
#Setting up repository smartgit password
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.
#Setting up repository smartgit code
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 Once you have confirmed this page, you will be redirected to Organization repositories won’t show up/can’t be accessed. Be sure to also GrantĪccess to all of your organizations, otherwise the corresponding Have to confirm by Authorize Application. This should open up your default web browser where you will Provider dialog, have GitHub selected and invoke Generate API To set up the GitHub integration, go to Preferences, section The connection to or a custom GitHub Enterprise instance I even configured GPG signing inside WSL and wslgit worked just fine.SmartGit integrates GitHub workflows in various places, provided that Until then, I have to resort to solutions like wslgit, unfortunately it's not working for me with SmartGit. Of course none of this would be needed if SmartGit added proper WSL support like VS Code does in some places. Not sure what could be the best course of action here. The absolute path is redundant, because the Git executable is started in the repository's root directory. If it should be a Git replacement, then it should accept the parameters like Git. Support: I still think, this is a problem of wslgit. Could you consider adding an option to always use absolute paths instead of relative? It shouldn't be that time consuming to implement such feature. Me: As you can see from the issue I linked, it would not be redundant information. Git does not need this and it would be redundant information. Me: Is it possible to configure SmartGit to use absolute paths to files when invoking Git commands? This might help fix this issue: #37 I reached to SmartGit about this and it went like this: