SQL Source Control, GIT and Visual Studio Online

• 
  Command line.
  
  > git push
  
  I know.

  AlexYates September 27, 2017 21:42

  - 0 +
• 
  Just so I'm clear - there's no way to do this via the SQL Source Control UI?
  
  I'm assuming your "I know" comment was intended to head off any screams of disbelief/frustration.

  HWinkler September 27, 2017 21:48

  - 0 +
• 
  Maybe I should ask a different question - is there a way to configure SQL Source Control to synch with Visual Studio Online directly? I don't have to have GIT in the middle if I don't need to.

  HWinkler September 27, 2017 22:04

  - 0 +
• 
  Hi @HWinkler
  
  Can you please try:
  1- create a Personal access token https://docs.microsoft.com/en-us/vsts/accounts/use-personal-access-tokens-to-authenticate
  2- clone the repository to your PC (manual clone or via VS)
  
  
  
  2- Click the database, go to Set up in SQL Source Control --Link to my source control system -- Git, paste the path of the local repository that you've cloned.
  
  
  
  3- Click 'Link', and choose access token and put in your Personal access token.
  SQL Source Control will remember the token so you don't need to re-enter it in the case of relinking.
  
  I hope this helps. Please let me know if you need more information.
  
  Thanks.
  
  

  Tianjiao_Li October 06, 2017 10:57

  - 0 +
• 
  Tianjiao - does this actually work with SQL Source control version 5.7.6.6321? That is the version the OP had and what I have, but my screen for linking the database is different and does not give me an option to use a personal access token.

  Shaun5Stu August 21, 2018 14:40

  - 0 +
• 
  Hi @Shaun5Stu
  
  Sorry I should have been more clearer. You won't be prompted Access Token request until you try to Push or Pull from remote.
  
  For example:
  
  
  After click Continue, you'll need to use Access token to complete the Push.
  
  
  

  Tianjiao_Li September 14, 2018 10:30

  - 0 +
• 
  I have the same issue.  Using the Git Push in Powershell is works. When I use the Access Token it fails very fast... Almost too fast.  Makes me wonder if its even trying.  I also tried using the Username and password which I created the VSTS (Azure DevOps) repository with... No luck

  LlewellynAtBluestone September 28, 2018 06:43

  - 0 +
• 
  Oddly the Pull from remote repository works so I assume all my credentials are good and the Push has a bug

  LlewellynAtBluestone September 28, 2018 06:46

  - 0 +
• 
  Same issue here, any more feedback on this one? Is it confirmed as a bug? am I doing something dumb? 
  
  ....Update - looks like I am doing something dumb. Though it would be MEGA helpful if SQL Source Control gave you the FULL error message & not just a simple 403.

  SinisterPenguin November 14, 2018 11:44

  - 0 +
• 
  I'm trying to get SSC (v7.0.6.8775) set-up to push to an Azure DevOps git repo. I have linked the repo successfully and committed changes but when I try to push changes I get to the same Continue button as per the first screenshot from @Tianjiao_Li but never get an option to add credentials and just get an authentication failure message. Any ideas as to how to solve this? I have previously been successfully committing to a TFS git repo through a git command line.
  

  chris_godfree January 03, 2019 11:02

  - 0 +
• 
  SQL Source Control 7 now uses the Git command line for all its operations. Have you been able to push successfully using the command line?

  Mike U January 12, 2019 09:59

  - 0 +
• 

  Mike U said:

  SQL Source Control 7 now uses the Git command line for all its operations. Have you been able to push successfully using the command line?

  
  Hi Mike, yes, I've been able to push successfully using the command line.

  chris_godfree January 14, 2019 08:58

  - 0 +
• 
  Are you prompted for any credentials while pushing from the command line? You may need to modify the relevant git.config so that it remembers credentials.

  Mike U January 14, 2019 13:50

  - 0 +

Add comment

Please sign in to leave a comment.