StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POGit push: set target for branch
primarykey
Id
8170558
data
AcceptedAnswerId
8172215
AnswerCount
4
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-11-17T16:19:33.917
FavoriteCount
8
LastActivityDate
2015-11-24T07:40:08.987
LastEditDate
2011-11-17T18:27:18.590
LastEditorUserId
1050687
OwnerUserId
1050687
ParentId
0
PostTypeId
1
Score
25
ViewCount
24519
LastEditorDisplayName
text
Body
I'd like to push my current branch (hp1) with <pre><code>git push </code></pre> and not <pre><code>git push origin hp1:team/hp1 </code></pre> The remote branch already exists. My local branches: <pre><code>develop master * hp1 </code></pre> git remote show origin tells me: <pre><code>Remote branches: develop tracked master tracked team/h2 tracked team/hp1 tracked team/n1 tracked Local branches configured for 'git pull': develop merges with remote develop master merges with remote master hp1 merges with remote team/hp1 Local refs configured for 'git push': master pushes to master (up to date) </code></pre> I already tried <pre><code>git branch --set-upstream hp1 origin/team/hp1 </code></pre> and <pre><code>git branch --set-upstream hp1 refs/remotes/origin/team/hp1 </code></pre> but both don't work. My colleague has a local branch called as the remote branch (team/hp1) and the code above works for him. He gets at the end an additional <pre><code>Local refs configured for 'git push': develop pushes to develop (up to date) master pushes to master (up to date) team/hp1 pushes to team/hp1 (up to date) </code></pre> So maybe you can tell me what's wrong and how to fix it. EDIT my config: <pre><code>[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] fetch = +refs/heads/*:refs/remotes/origin/* url = ***@***:***.git [branch "master"] remote = origin merge = refs/heads/master [branch "hp1"] remote = origin merge = refs/heads/team/hp1 </code></pre>
Tags
<git>
Title
Git push: set target for branch
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USm1schka
UserOwnerUserId
1. USm1schka
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POGit push: set target for branch
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POGit push: set target for branch
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POGit push: set target for branch
 UserUserId
 USYa Zhuang
 VoteTypeVoteTypeId
 VTFavorite
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.