avatar brianteeman
brianteeman
9 Mar 2014

I had assumed that the issue status would be reflected on github as a label - it doesnt look like changing the issue status on the tracker has any effect on the issue at github

avatar brianteeman brianteeman - open - 9 Mar 2014
avatar mbabker
mbabker - comment - 9 Mar 2014

Aside from open/closed status (their "proper" statuses), labels aren't
hooked up to our own internal statuses right now.

On Sat, Mar 8, 2014 at 11:38 PM, Brian Teeman notifications@github.comwrote:

I had assumed that the issue status would be reflected on github as a
label - it doesnt look like changing the issue status on the tracker has
any effect on the issue at github

Reply to this email directly or view it on GitHub#319
.

avatar b2z
b2z - comment - 9 Mar 2014

I do not know GitHub API so well, but is it really possible to map our statuses to GitHub's labels?

avatar mbabker
mbabker - comment - 9 Mar 2014

Sure, on a save action the status is pushed up to GitHub as a label via the API (we already push labels in the CMS PR hooks). Where it gets hard is having to switch from the authenticated user to a bot account to add the label in case the authenticated user doesn't have permissions on GitHub to manage labels.

avatar b2z
b2z - comment - 9 Mar 2014

Nice, but this permission problem is annoying :(

avatar b2z
b2z - comment - 10 Mar 2014

Where it gets hard is having to switch from the authenticated user to a bot account to add the label

If we will solve it this will be a little victory for us. Need to dig in.

avatar b2z
b2z - comment - 18 Aug 2014

Closed via #389

avatar b2z b2z - change - 18 Aug 2014
Status New Closed
Closed_Date 0000-00-00 00:00:00 2014-08-18 19:17:38
avatar b2z b2z - close - 18 Aug 2014

Add a Comment

Login with GitHub to post a comment