Opened 8 years ago

Closed 7 years ago

#15943 closed defect (invalid)

git: creating new remote branch should associate it with subsequent pushes

Reported by: rws Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: scripts Keywords: git, dev, branch, push
Cc: SimonKing Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description

From Simon King, in https://groups.google.com/forum/?hl=en#!topic/sage-devel/sTLT83d1g14

Apparently you need to use git "the hard way" to let your local branch be pushed to a public branch on trac, and then you have to manually edit the branch field on trac to point to the public branch.

I keep forgetting how to do this. Hence, I'd very much appreciate if someone could implement something like

  sage -dev push --ticket=12345 --remote_branch=public/foo/bar 

to push to the specified public branch, and (as a convenience) update the information on the local branch, such that subsequently

  sage -dev push 
and 
  git push 

will both push to the previously indicated public trac branch.

And similarly, if the user has write permission to the branch (e.g., public branch) attached to a ticket, then

  sage -dev push

should push *there* (and not to a new branch u/UserName/...).

Change History (4)

comment:1 Changed 8 years ago by SimonKing

  • Cc SimonKing added

comment:2 Changed 7 years ago by rws

  • Milestone changed from sage-6.2 to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

This is no longer a problem. Just use git trac.

comment:3 Changed 7 years ago by rws

  • Status changed from needs_review to positive_review

comment:4 Changed 7 years ago by vbraun

  • Resolution set to invalid
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.