I have found the instructions at https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md useful for me, as someone used to the old trac interface.
On Saturday, April 8, 2023 at 1:23:06 PM UTC-7 G. M.-S. wrote: > > Thanks Dima and Drew. > > I had the very same question, but zero ways for doing it, so I did not > dare ask… > > Guillermo > > On Sat, 8 Apr 2023 at 22:14, Dima Pasechnik <dim...@gmail.com> wrote: > >> >> On Sat, 8 Apr 2023, 20:24 Drew Shotwell, <drewsh...@gmail.com> wrote: >> >>> I'm looking into working on an issue in git, and I'm wondering how to >>> properly go about testing someone else's branch. Let's take for instance >>> https://github.com/sagemath/sage/pull/35414. >> >> >> suppose you have remote foo set to >> https://github.com/sagemath/sage >> <https://github.com/sagemath/sage/pull/35414> >> >> then >> >> git fetch foo pull/35414 <https://github.com/sagemath/sage/pull/35414> >> /head:pr35414 >> >> will create the branch named pr35414 you want >> >> >> Essentially what I want to do is get the code changes from the forked >>> branch videlec:complex-root-of-to-algebraic into my repository so I can >>> test them in parallel with the develop branch. My own research has opened >>> an overwhelming number of different ways for doing this, so I figured I'd >>> ask here to get the most straight forward answer. Thank you. >> >> > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/04a58ebe-6365-4439-904a-2f8827dd2a47n%40googlegroups.com.
