Awesome it worked - thanks so much!

Do you know how long they'll be supporting this version now?


On Apr 23, 7:05 pm, Christian Hammond <chip...@chipx86.com> wrote:
> Hey Florian,
>
> I have a workaround for you, if you're on Linux or otherwise have curl.
>
> Simply do:
>
>     curl -u <github_username>https://api.github.com/legacy/token
>
> Enter your GitHub password. It should spit out an API token, and you should
> be set.
>
> Christian
>
> --
> Christian Hammond - chip...@chipx86.com
> Review Board -http://www.reviewboard.org
> VMware, Inc. -http://www.vmware.com
>
> On Mon, Apr 23, 2012 at 6:52 PM, Christian Hammond <chip...@chipx86.com>wrote:
>
>
>
>
>
>
>
> > Right, the API tokens aren't listed. They have an API that will return a
> > token. So, we're going to have to wire up a button for getting that token,
> > given your credentials. Easier change, and quicker to get in.
>
> > Christian
>
> > --
> > Christian Hammond - chip...@chipx86.com
> > Review Board -http://www.reviewboard.org
> > VMware, Inc. -http://www.vmware.com
>
> > On Mon, Apr 23, 2012 at 6:50 PM, Florian Leibert <f...@leibert.de> wrote:
>
> >> I don't see anything on the Github page indicating API tokens... Just
> >> the previous oAuth stuff.
>
> >> On Apr 23, 3:14 pm, Christian Hammond <chip...@chipx86.com> wrote:
> >> > Hey,
>
> >> > So, I have a patch up for review (
> >>http://reviews.reviewboard.org/r/3073/)
> >> > that works with the v3 API, but at the moment this patch only applies
> >> > cleanly against the 1.7.x branch, and a couple things need to be fixed.
>
> >> > However, I just heard from GitHub that there's a new API introduced that
> >> > will provide the API token. So I'll be shifting my priorities to making
> >> > this accessible from the repository page for 1.6.x so that we can cut a
> >> > release that will let you get the token. Once that's out, we'll refocus
> >> on
> >> > the new v3 API and work on getting that into a release.
>
> >> > Christian
>
> >> > --
> >> > Christian Hammond - chip...@chipx86.com
> >> > Review Board -http://www.reviewboard.org
> >> > VMware, Inc. -http://www.vmware.com
>
> >> > On Sun, Apr 22, 2012 at 11:50 PM, Christian Hammond <chip...@gmail.com
> >> >wrote:
>
> >> > > Nothing new from GitHub on the API tokens yet, but from our side I've
> >> made
> >> > > significant progress. However, it'd still not finished. This isn't a
> >> quick
> >> > > fix sort of thing, but rather something that has to be designed and
> >> tested
> >> > > carefully.
>
> >> > > I was hoping to have a patch up by today, but there were some road
> >> blocks.
> >> > > I'm quite close, though, and we'll see where I am by about 4AM.
>
> >> > > I'll send a reply when there's something up.
>
> >> > > Christian
>
> >> > > On Apr 22, 2012, at 23:21, Florian Leibert <f...@leibert.de> wrote:
>
> >> > > > Any news on this?
>
> >> > > > On Apr 20, 11:51 am, Christian Hammond <chip...@chipx86.com> wrote:
> >> > > >> Hi Florian,
>
> >> > > >> I'm working every day on it. There's a bit to do. However, I think
> >> by
> >> > > this
> >> > > >> weekend I'll at the very least have a patch up for review that you
> >> can
> >> > > try
> >> > > >> out, if you want to be an early tester. I'm shooting for a release
> >> by
> >> > > early
> >> > > >> next week (hopefully).
>
> >> > > >> GitHub tells me they're looking into bringing API Tokens back to
> >> the
> >> > > >> Account page soon, but I don't quite know when that will happen.
>
> >> > > >> Christian
>
> >> > > >> --
> >> > > >> Christian Hammond - chip...@chipx86.com
> >> > > >> Review Board -http://www.reviewboard.org
> >> > > >> VMware, Inc. -http://www.vmware.com
>
> >> > > >> On Fri, Apr 20, 2012 at 8:01 AM, Florian Leibert <f...@leibert.de>
> >> > > wrote:
> >> > > >>> Hi -
> >> > > >>> we' were going to install reviewboard but have no access to our
> >> ApiV2
> >> > > >>> token. What's the ETA for getting RB working with the V3 github
> >> API?
>
> >> > > >>> Thanks!
> >> > > >>> Florian
>
> >> > > >>> --
> >> > > >>> Want to help the Review Board project? Donate today at
> >> > > >>>http://www.reviewboard.org/donate/
> >> > > >>> Happy user? Let us know athttp://www.reviewboard.org/users/
> >> > > >>> -~----------~----~----~----~------~----~------~--~---
> >> > > >>> To unsubscribe from this group, send email to
> >> > > >>> reviewboard+unsubscr...@googlegroups.com
> >> > > >>> For more options, visit this group at
> >> > > >>>http://groups.google.com/group/reviewboard?hl=en
>
> >> > > > --
> >> > > > Want to help the Review Board project? Donate today at
> >> > >http://www.reviewboard.org/donate/
> >> > > > Happy user? Let us know athttp://www.reviewboard.org/users/
> >> > > > -~----------~----~----~----~------~----~------~--~---
> >> > > > To unsubscribe from this group, send email to
> >> > > reviewboard+unsubscr...@googlegroups.com
> >> > > > For more options, visit this group at
> >> > >http://groups.google.com/group/reviewboard?hl=en
>
> >> --
> >> Want to help the Review Board project? Donate today at
> >>http://www.reviewboard.org/donate/
> >> Happy user? Let us know athttp://www.reviewboard.org/users/
> >> -~----------~----~----~----~------~----~------~--~---
> >> To unsubscribe from this group, send email to
> >> reviewboard+unsubscr...@googlegroups.com
> >> For more options, visit this group at
> >>http://groups.google.com/group/reviewboard?hl=en

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~----------~----~----~----~------~----~------~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en

Reply via email to