#15943: git: creating new remote branch should associate it with subsequent
pushes
-----------------------+------------------------------------------
Reporter: rws | Owner:
Type: defect | Status: new
Priority: major | Milestone: sage-6.2
Component: scripts | Keywords: git, dev, branch, push
Merged in: | Authors:
Reviewers: | Report Upstream: N/A
Work issues: | Branch:
Commit: | Dependencies:
Stopgaps: |
-----------------------+------------------------------------------
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/...).
--
Ticket URL: <http://trac.sagemath.org/ticket/15943>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
