StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14442631
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-21T16:09:41.917
FavoriteCount
0
LastActivityDate
2013-01-21T16:09:41.917
LastEditDate
LastEditorUserId
0
OwnerUserId
693538
ParentId
14438120
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It probably doesn't answer your answer directly, but I think that this particular situation can be ruled with such feature of Git as <a href="http://git-scm.com/book/en/Git-Tools-Submodules" rel="nofollow">submodules</a>. In this case you need to have two different repositories hosted somewhere, anyway. But with help of submodules you can tell Git that files of one repo should be located inside the directory tree of another one. Without causing the mess you described! For example, assuming that you have your projects hosted as <code>github.com/user/Client</code> and <code>github.com/user/Server</code> repos. Go to the folder of <code>Client</code> repository and do the following: <pre><code>git submodule add git@github.com:user/Server.git src/server </code></pre> This will clone the repo with given address into the folder you specified (<code>src/server</code> in this example). After that you have to commit changes. Although a lot of files were added, there will not be lots of changes in commit diff: there will be only a short record in special file saying that such repository now is a submodule. That is, files of <code>Server</code> not actually stored in <code>Client</code> repo, only the reference to them is stored. This is the power of git submodules. Note that after that, when you clone your <code>Client</code> repo somewhere else, its submodule will not be fetched by default. You have to use <code>git submodule update --init</code> to initialize submodules. Also note that the reference to <code>Server</code> submodule points to a specific revision of it. After you made some changes to <code>Server</code> repo you may want to go to <code>Client</code> repo, navigate to directory of submodule (<code>src/server</code> in this example) and do a simple <code>git pull</code> and commit changes in <code>Client</code> repo. Again, there will be no giant diff, only the new reference to submodule will be commited. As an example of the repo with submodules you can check out my repo for Vim settings directory: it has many plugins inside its <a href="https://github.com/NIA/dotvim/tree/master/bundle" rel="nofollow">bundle</a> folder and all of them are git submodules. GitHub shows them pretty well and allows easy one-click navigation to submodule repo if it is GitHub-hosted. P.S. If this all has nothing in common with what you want, and you simply want a folder <code>Server</code> to be added to repo <code>Client</code>, you can just copy <code>Server</code> to client and delete all traces of Git from <code>Server</code> directory (if there were some) by deleting <code>.git</code> inside it. Now you simply have one repo, commit all this lots of changes and go on. The drawback of this is complete loss of history of <code>Server</code> repo — it is not a big pain at the initial phase of project.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POadd new Project to existing github Repo
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USNIA
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
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.