Re: Having trouble setting up a GitHub (Private Organization) repository

2012-04-15 Thread Christian Hammond
Okay, so here's the situation.

I talked to GitHub and they're indeed switching to the new API, which we
are not yet using. My plan was to move to this in a 1.7.x release, but
that's too far off. Fortunately, I had some detailed plans worked out, so
I'll be spending some time on putting this into 1.6.6. I already have a
good amount of code from last night put toward this.

I've requested that GitHub list the API token somewhere until the removal,
and asked for a time extension (possibly just on the API we need). So,
we'll see if that's doable. If not, I'll do what I can to make this all
work before May 1st, but at the moment there's no way I can tell to get the
API token, unless they bring that back. They were very responsive and
understanding about all this, so I think we can work something out.

Will keep everyone updated on this.

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com


On Sun, Apr 15, 2012 at 12:31 AM, Christian Hammond chip...@chipx86.comwrote:

 Hmm, it is possible. I'll contact them and see if I can find out. I'm
 working on plans for moving to API v3,  but I'm greatly concerned about the
 timing, as I'm not confident we'll get that in by then.

 Christian

 --
 Christian Hammond - chip...@chipx86.com
 Review Board - http://www.reviewboard.org
 VMware, Inc. - http://www.vmware.com



 On Sat, Apr 14, 2012 at 10:45 PM, Dan Z d...@modria.com wrote:

 Hi,

 The admin screen for setting up a GitHub (Private Organization)
 repository requires Your GitHub API token. There's a link to the
 page at GitHub where this token can be found -- except that the token
 isn't there. (The page name has even changed a little.) I can't figure
 out why the token isn't there -- except for this hint on the GitHub
 Blog: We will terminate API v1 and API v2 in 1 month on May 1st,
 2012.

 My first question is: does ReviewBoard use either the v1 or v2 GitHub
 API, or has it been updated to v3?

 Second question: Is it possible that GitHub has removed the API Token
 in preparation for this change? If so, that sort of answers my first
 question, since ther repository setup page on ReviewBoard is asking
 for an API Token.

 Thanks in advance for any info anyone can give.

 Best,
 Dan

 --
 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




-- 
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

Re: Issue 46 in reviewboard: 80-column indicator in diff view

2012-04-15 Thread reviewboard


Comment #17 on issue 46 by bernard3...@gmail.com: 80-column indicator in  
diff view

http://code.google.com/p/reviewboard/issues/detail?id=46

Speaking of cached content: This is often a project or company-wide  
setting, so maybe this could be a global setting (turn on, turn off, column  
size) would work for most cases and you can benefit from computing this  
server-side with the same content caching as normal.


--
You received this message because you are subscribed to the Google Groups 
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to 
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/reviewboard-issues?hl=en.