StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20223069
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-11-26T16:48:59.783
FavoriteCount
0
LastActivityDate
2013-11-26T16:48:59.783
LastEditDate
LastEditorUserId
0
OwnerUserId
227887
ParentId
20222732
PostTypeId
2
Score
37
ViewCount
0
LastEditorDisplayName
text
Body
So-called "Fast-forward" merges don't produce a commit, whereas other merges (often refered to as "octopus merge" (now you see why github's mascott is an octocat)) produce commits. Basically, a Fast-forward happens when your branches did not diverge. Say you want to merge a branch <code>foo</code> in the <code>master</code> branch. If these branches did not diverge, you would have an history like this (each <code>*</code> represents a commit): <pre><code>*---* (master) \ *---*---* (foo) </code></pre> In this situation, the merge is fast-forward because (according to the graph theory, which is the underlying foundation of a git graph), <code>master</code> is reachable from <code>foo</code>. In other words, you just have to move the <code>master</code> reference to <code>foo</code>, and you're done: <pre><code>*---* \ *---*---* (master, foo) </code></pre> When your branches diverge: <pre><code>*---*---* (master) \ *---*---* (foo) </code></pre> You have to create a commit to "join" the two branches: <pre><code> ↓ *---*---*-------* (master) \ / *---*---* (foo) </code></pre> The commit pointed by the arrow is the merge commit and has two parent commits (the former <code>master</code> branch tip, and the current <code>foo</code> branch tip). Note that you can force Git to create a merge commit for a fast-forward merge with the <code>--no-ff</code> option. I highly recommend reading <a href="http://think-like-a-git.net/">http://think-like-a-git.net/</a> for a good understanding of how the graph theory applies to git (you don't need to know the graph theory, everything you need to know is on the website), which will make working with Git incredibly easier :)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy does git merge sometimes create a commit, sometimes does not?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USGeoffrey Bachelet
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWhy does git merge sometimes create a commit, sometimes does not?
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTDownMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.