StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17643418
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
4
CommunityOwnedDate
CreationDate
2013-07-14T20:25:35.770
FavoriteCount
0
LastActivityDate
2016-03-14T21:22:00.673
LastEditDate
2017-05-23T11:46:28.603
LastEditorUserId
-1
OwnerUserId
0
ParentId
10832722
PostTypeId
2
Score
14
ViewCount
0
LastEditorDisplayName
user456814
text
Body
While <a href="https://stackoverflow.com/users/11343/charlesb">CharlesB's solution is correct and probably easier</a>, the reason that the original poster is seeing the commit message before the commit he wants to edit is because he's using the <code>--amend</code> flag of <code>git commit</code>, which modifies the previous commit. Instead of using <code>--amend</code> to commit your changes, just use <code>git commit</code> without the flag, which won't touch the previous commit. You can also pass in an option to reuse the commit message from the commit that you reset using <code>git reset head^</code>: <pre class="lang-bash prettyprint-override"><code>git commit --reuse-message=HEAD@{1} # Or use -C, which is the same thing, but shorter: git commit -C HEAD@{1} </code></pre> <code>HEAD@{1}</code> points to the commit you were at before you did <code>git reset head^</code>. You can also just pass in the sha id for that commit directly. From <a href="https://www.kernel.org/pub/software/scm/git/docs/git-commit.html" rel="nofollow noreferrer">the <code>git commit</code> docs</a>: <blockquote> <pre><code>-C <commit> --reuse-message=<commit> </code></pre> Take an existing commit object, and reuse the log message and the authorship information (including the timestamp) when creating the commit. </blockquote> Of course, like I said, CharlesB's solution is simpler, since if you don't do the first <code>git reset head^</code>, you can just make changes and amend the commit you're trying to modify directly, and you automatically get the previous commit message when you do <code>git commit --amend</code>, you don't have to pass in the commit sha for it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow do I keep the commit message when editing commits via git rebase --interactive?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. This table or related slice is empty.
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POHow do I keep the commit message when editing commits via git rebase --interactive?
 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
 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.