-
Notifications
You must be signed in to change notification settings - Fork 14
Using git-tfs #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
andresmoschini
wants to merge
1
commit into
MakingSense:master
Choose a base branch
from
andresmoschini:using-git-tfs
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Using git-tfs #43
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
--- | ||
layout: default | ||
title: Using TFS and Git together | ||
--- | ||
|
||
If you need continue checking-in to TFS along you work with Git, you can use git-tfs as a bridge. | ||
|
||
It supposed that git-tfs supports to check-in in name of another developer, but for some reason (maybe TFS permissions, maybe it is not ready yet, maybe my fault) it didn't work for me, so, in our team we decided that each developer check-in in TFS his changes after merge his pull requests. | ||
|
||
### 1. Prepare environment for developers | ||
|
||
* Clone GitHub repository <!-- TODO --> | ||
* Bootstrap git-tfs <!-- TODO --> | ||
|
||
### 2. Work in a feature | ||
|
||
<!-- TODO (fetch remotes, fetch tfs, start a new branch, commit changes) --> | ||
|
||
### 3. Create a pull request | ||
|
||
<!-- TODO (Rebase or merge upstream changes, create the pull request, discuss) --> | ||
|
||
### 4. Merge pull request and check-in in TFS | ||
|
||
<!-- TODO (Merga the pull request, fetch remotes, fetch tfs, check-in in TFS, push to upstream) --> | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
--- | ||
layout: default | ||
title: Clone a TFS repository to GitHub | ||
--- | ||
|
||
|
||
### 1. Clone TFS to a local git repository | ||
|
||
The command [clone](https://github.com/git-tfs/git-tfs/blob/master/doc/commands/clone.md) allows to clone a branch with all _changesets_. | ||
|
||
 | ||
|
||
The same command allows to [clone all the branches](https://github.com/git-tfs/git-tfs/blob/master/doc/commands/clone.md#clone-all-the-branches-and-merge-changesets)) (but I didn't test it). | ||
|
||
 | ||
|
||
But it used to fail: | ||
|
||
 | ||
|
||
If you don't need the complete history, it is possible to get only the last _changeset_ with the command [quick-clone](https://github.com/git-tfs/git-tfs/blob/master/doc/commands/quick-clone.md). | ||
|
||
 | ||
|
||
### 2. Prepare repository for Git | ||
|
||
<!-- TODO (git configuration files, delete files, etc) --> | ||
|
||
### 3. Create a new GitHub repository | ||
|
||
<!-- TODO --> | ||
|
||
### 4. Push local cloned commits to GitHub repository | ||
|
||
<!-- TODO --> | ||
|
Binary file added
BIN
+13.9 KB
migration-to-git/3-working-with-git/git-tfs-clone-with-branches-broken.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is being redacted in first person, maybe we should include who the author is?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are right, I will try to remove subjectiveness from git-fts-to-github articule and move git-fts-as-bridge article under DCA flow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it is not redacted in first person... for example, it starts with "Prepare..." instead "I prepare...", another sentence says: "Work..." instead "I work..." Maybe I am wrong...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hehe, it is not well redacted. But JD is fine, the original idea of this file was to describe how we (DCA team) are using git-tfs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The examples that I found:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, ok... I had not read the whole document.