Answers: <p>I'm using <a href="https://docs.gitlab.com/ee/workflow/repository_mirroring.html#pushing-to-a-remote-repository" rel="nofollow noreferrer">https://docs.gitlab.com/ee/workflow/repository_mirroring.html#pushing-to-a-remote-repository</a> to push everything into a repository in VSTS, easily done via access token with the right permissions.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-06-26T14:43:59.507Z
Answers: 2018-06-26T14:43:59.507Z
Answers: dano0b
Answers: <blockquote>
    <p>I have a repository in GitLab that is used by our development team. On
    the other hand, there is a VSTS setup (at xyz.visualstudio.com) that
    we use to manage our scrum board.</p>
  </blockquote>
  
  <p>First impression is that you should either choose one repository or check the API of both products to investigate whether the tools could be integrated. From a DevOps perspective, repetitive processes like this that are done manually over and over again should be automated.</p>
  
Answers: CC BY-SA 3.0
Answers: 2018-04-26T21:04:26.857Z
Answers: 2018-04-26T21:04:26.857Z
Answers: 030
Body: <p>I have a repository in GitLab that is used by our development team. On the other hand, there is a VSTS setup (at xyz.visualstudio.com) that we use to manage our scrum board. </p>
  
  <p>As of today, we have to manually import the repository in VSTS every time a feature is finalized. Once the repository is imported, it does not pull the latest commits by itself. </p>
  
  <p>How do I ensure that every time a developer commits code to GitLab repository, same is displayed in VSTS automatically? Am I missing something when I use "import repository" feature in VSTS?</p>
  
Comments: CC BY-SA 4.0
Comments: 2019-12-23T08:42:54.910Z
Comments: Could you indicate whether you solved the issue?
Comments: 030
Comments: CC BY-SA 4.0
Comments: 2019-12-24T10:23:05.967Z
Comments: Hi. I was not able to solve this issue. We ended up just creating a pipeline to check in code to VSTS from Git.
Comments: jitendragarg
Comments: CC BY-SA 3.0
Comments: 2018-04-30T15:14:12.747Z
Comments: I think the thing you want is a gitlab runner https://docs.gitlab.com/runner. They execute every time new code is pushed to the repo, you can configure them to do anything you want.
Comments: Jacob Vanus
Tags: <gitlab><azure-devops>
Title: Reflect GitLab repo changes in VSTS code
UserDisplayName: jitendragarg
ThreadText: # Reflect GitLab repo changes in VSTS code
  
  (Asked by: username_0 on 2018-01-10)
  
  I have a repository in GitLab that is used by our development team. On the other hand, there is a VSTS setup (at xyz.visualstudio.com) that we use to manage our scrum board.
  
  As of today, we have to manually import the repository in VSTS every time a feature is finalized. Once the repository is imported, it does not pull the latest commits by itself.
  
  How do I ensure that every time a developer commits code to GitLab repository, same is displayed in VSTS automatically? Am I missing something when I use "import repository" feature in VSTS?
  
  **Tags:** gitlab, azure-devops
  
  > **Comments:**
  > **username_2**: I think the thing you want is a gitlab runner https://docs.gitlab.com/runner. They execute every time new code is pushed to the repo, you can configure them to do anything you want.  
  > **username_1**: Could you indicate whether you solved the issue?  
  > **username_0**: Hi. I was not able to solve this issue. We ended up just creating a pipeline to check in code to VSTS from Git.  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_3 on 2018-06-26. Score: 2
  
  I'm using <https://docs.gitlab.com/ee/workflow/repository_mirroring.html#pushing-to-a-remote-repository> to push everything into a repository in VSTS, easily done via access token with the right permissions.
  
  
  ---
  
  ### Answer by username_1 on 2018-04-26. Score: 1
  
  > I have a repository in GitLab that is used by our development team. On
  > the other hand, there is a VSTS setup (at xyz.visualstudio.com) that
  > we use to manage our scrum board.
  
  First impression is that you should either choose one repository or check the API of both products to investigate whether the tools could be integrated. From a DevOps perspective, repetitive processes like this that are done manually over and over again should be automated.
  
  
  ---
  
  