StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18736202
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-11T08:27:11.763
FavoriteCount
0
LastActivityDate
2013-09-11T08:27:11.763
LastEditDate
LastEditorUserId
0
OwnerUserId
2609675
ParentId
18729758
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Delete the folder from the repository, add it to .gitignore and then commit the changes. Push that commit to your central bare repo and you are (almost) fine. The reason why git shows uncommited changes when you delete the folder is, that you in fact have changed something. You deleted the folder. gitignore doesn't stop that from happening. In fact, if you add a tracked file to <code>.gitignore</code>, git will not ignore that file (same applies for folders). <code>.gitignore</code> only works for untracked files. So, to untrack files inside a repository, you have to delete them (or at least make git think so) and add them to <code>.gitignore</code>. You can do that without actually deleting the files from the working directory: <pre><code>git rm --cached <files> </code></pre> The actual files will remain inside the working directory, but <code>git status</code> will show them as deleted. If you add them to <code>.gitignore</code> at the same time, the files will remain there forever, without git noticing it. However, if you commit that change and it gets pulled to somewhere else, the files will get deleted because git thinks you actually have deleted them. So you will need to get these files back (This will not make git track these files again as they are added to <code>.gitignore</code>): <pre><code>git checkout HEAD~1 <files> </code></pre> That will get the files back on that single repo. You will have to do that for every repo that pulled the commit you made above.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POKeeping downstream Puppet git repositories in sync except for ignored directories
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USOznerol256
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POKeeping downstream Puppet git repositories in sync except for ignored directories
 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
 VTAcceptedByOriginator
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.