StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15778570
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-04-03T03:55:51.307
FavoriteCount
0
LastActivityDate
2018-05-17T12:32:25.620
LastEditDate
2018-05-17T12:32:25.620
LastEditorUserId
909252
OwnerUserId
845488
ParentId
15772134
PostTypeId
2
Score
108
ViewCount
0
LastEditorDisplayName
text
Body
There are two ways of handling this. Which is easier depends on your situation Reset If the commit you want to get rid of was the last commit, and you have not done any additional work you can simply use <code>git-reset</code> <pre><code>git reset HEAD^ </code></pre> Takes your branch back to the commit just before your current HEAD. However, it doesn't actually change the files in your working tree. As a result, the changes that were in that commit show up as modified - its like an 'uncommit' command. In fact, I have an alias to do just that. <pre><code>git config --global alias.uncommit 'reset HEAD^' </code></pre> Then you can just used <code>git uncommit</code> in the future to back up one commit. Squashing Squashing a commit means combining two or more commits into one. I do this quite often. In your case you have a half done feature commited, and then you would finish it off and commit again with the proper, permanent commit message. <pre><code>git rebase -i <ref> </code></pre> I say above because I want to make it clear this could be any number of commits back. Run <code>git log</code> and find the commit you want to get rid of, copy its SHA1 and use it in place of <code><ref></code>. Git will take you into interactive rebase mode. It will show all the commits between your current state and whatever you put in place of <code><ref></code>. So if <code><ref></code> is 10 commits ago, it will show you all 10 commits. In front of each commit, it will have the word <code>pick</code>. Find the commit you want to get rid of and change it from <code>pick</code> to <code>fixup</code> or <code>squash</code>. Using <code>fixup</code> simply discards that commits message and merges the changes into its immediate predecessor in the list. The <code>squash</code> keyword does the same thing, but allows you to edit the commit message of the newly combined commit. Note that the commits will be re-committed in the order they show up on the list when you exit the editor. So if you made a temporary commit, then did other work on the same branch, and completed the feature in a later commit, then using rebase would allow you to re-sort the commits and squash them. WARNING: Rebasing modifies history - DONT do this to any commits you have already shared with other developers. Stashing In the future, to avoid this problem consider using <code>git stash</code> to temporarily store uncommitted work. <pre><code>git stash save 'some message' </code></pre> This will store your current changes off to the side in your stash list. Above is the most explicit version of the stash command, allowing for a comment to describe what you are stashing. You can also simply run <code>git stash</code> and nothing else, but no message will be stored. You can browse your stash list with... <pre><code>git stash list </code></pre> This will show you all your stashes, what branches they were done on, and the message and at the beginning of each line, and identifier for that stash which looks like this <code>stash@{#}</code> where # is its position in the array of stashes. To restore a stash (which can be done on any branch, regardless of where the stash was originally created) you simply run... <pre><code>git stash apply stash@{#} </code></pre> Again, there # is the position in the array of stashes. If the stash you want to restore is in the <code>0</code> position - that is, if it was the most recent stash. Then you can just run the command without specifying the stash position, git will assume you mean the last one: <code>git stash apply</code>. So, for example, if I find myself working on the wrong branch - I may run the following sequence of commands. <pre><code>git stash git checkout <correct_branch> git stash apply </code></pre> In your case you moved around branches a bit more, but the same idea still applies. Hope this helps.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCan I delete a git commit but keep the changes
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSteven
UserOwnerUserId
1. USeddiemoya
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.