How do I sync a TFS repo to github?

Question

0.00/5 (No votes)

See more:

I have a visual studio online repo (TFS) that I use for my "CQRS on Azure" stuff but folks are looking for a GitHub version so they can contribute - is it possible to set something up to keep them both in sync?

I want to keep the "fast ring" on TFS but push to GitHub as a build step on a successful build.

What I have tried:

Looked on google - didn't understand any of the potential suggestions. Maybe this is not possible or not sensible?

Posted 2-Apr-16 10:57am

Duncan Edwards Jones

Updated 5-Aug-16 5:32am

v2

Add a Solution

2 solutions

Solution 2

Have a look at git-tfs[^] which seems like a reasonable way to keep two repo's on the different plaforms in sync. It's not that hard to setup and use.

Posted 5-Aug-16 5:32am

calway

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Accepted Answer · 2016-04-02T11:09:00

One of these two Revision Control systems has nothing to do with another one.

Therefore, to sync them, update code from one of the repositories and commit updated code to another one. That's all.

In a way, this is sensible but cannot be considered as a part of any reasonable development workflow. It can even be considered as defeat of the purpose of Revision Control systems. Practically, it could be just a workflow noise which creates no value at all, only introduces additional source of human-generated errors.

Get rid of it. Pick one of the systems and conduct your development using it. If you asked me on the choice, I would always advise to use open-source solution. If you already using github, switching to git would give you double benefits. First, you would resort to purely open-source system, very popular, constantly peer-reviewed and improved, and hence very reliable; at the same time, you will have identical system for internal development and github. You won't need to install much; the system is extremely lightweight. Or, as an option, base all your development exclusively on github itself, if you find dependency on this resource acceptable.

If you want added reliability, add backup, not of any project code, but of the code database itself.

—SA