Closed budherz closed 10 years ago
Strange. I can't reproduce that problem here. Could you post the url of a GitHub issue that doesn't work for you?
Thanks for taking the time to report your problem!
Unfortunately I can't since it's our private repo. I was just wondering if you had more documentation I could run through?
Thanks for the response!
On Thu, Jun 27, 2013 at 2:10 PM, Andrew SB notifications@github.com wrote:
Strange. I can't reproduce that problem here. Could you post the url of a GitHub issue that doesn't work for you?
Thanks for taking the time to report your problem!
— Reply to this email directly or view it on GitHubhttps://github.com/andrewsomething/bug2trello/issues/4#issuecomment-20143962 .
Ah, that's probably the problem. I don't have any private repos, so I can't test that right now. I'll probably have to set up an OAuth request to ask for authorization for accessing private issues.
Could you give me a "sanitized" version of the url, just so I can see the format? The code that parses the url to decide what function to use to get the bug info, checks for:
else if(parser.hostname == 'github.com' && (parser.pathname.indexOf('issues') > -1))
It could possibly just need to be less strict if the url for private issues look a bit different.
I'll see what I can send you when I get a chance.
On Thu, Jun 27, 2013 at 2:54 PM, Andrew SB notifications@github.com wrote:
Ah, that's probably the problem. I don't have any private repos, so I can't test that right now. I'll probably have to set up an OAuth request to ask for authorization for accessing private issues.
Could you give me a "sanitized" version of the url, just so I can see the format? The code that parses the url to decide what function to use to get the bug info, checks for:
else if(parser.hostname == 'github.com' && (parser.pathname.indexOf('issues') > -1))
It could possibly just need to be less strict if the url for private issues look a bit different.
— Reply to this email directly or view it on GitHubhttps://github.com/andrewsomething/bug2trello/issues/4#issuecomment-20147006 .
Interesting - This issue can be added to the Welcome board on Trello. Also successfully added it to our boards. I can't add our issues to any of our boards though. I'll investigate further as I have time and let you know.
Drowning in work right now, but this would be a great help to our PM team. Nice job.
On Fri, Jun 28, 2013 at 8:43 AM, Bud Herz budh@tricyclestudios.com wrote:
I'll see what I can send you when I get a chance.
On Thu, Jun 27, 2013 at 2:54 PM, Andrew SB notifications@github.comwrote:
Ah, that's probably the problem. I don't have any private repos, so I can't test that right now. I'll probably have to set up an OAuth request to ask for authorization for accessing private issues.
Could you give me a "sanitized" version of the url, just so I can see the format? The code that parses the url to decide what function to use to get the bug info, checks for:
else if(parser.hostname == 'github.com' && (parser.pathname.indexOf('issues') > -1))
It could possibly just need to be less strict if the url for private issues look a bit different.
— Reply to this email directly or view it on GitHubhttps://github.com/andrewsomething/bug2trello/issues/4#issuecomment-20147006 .
Keeping the bug in the loop of a recent email exchange:
On Sun, Mar 2, 2014 at 12:49 PM, Paul XXXXXX XXXXXXy@XXXXXX.com wrote:
Or do you have any thoughts of how much work it might be? Thank you, Paul.
On Tue, Feb 25, 2014 at 2:00 PM, Paul XXXXXX XXXXXX@XXXXXX.com wrote:
Andrew: Do you plan to support private github repo's at some point in the future? Can we motivate you to get this feature in?
Hi Paul,
I don't have any private repositories GitHub. So it hasn't been a priority obviously. Though I do plan on getting around to it at some point. Currently for GitHub, Bug 2 Trello uses the json api to get information about the issue. I think that it's probably not worth it to deal with authenticating to GitHub. It would probably be simpler to just scrap information from the html page. In fact, as I was typing, I realized that's so simple that I just did it. Would you be interested in testing it?
Are the urls for private issues in the same format as public ones? e.g.:
https://github.com/$repo_owner)/$(project)/issues/4$(number)
If not, I'll need to do one more thing.
You can test it by grabbing this branch:
git clone https://github.com/andrewsomething/bug2trello.git -b private-issues
Then go to chrome://extensions/ and check the "Developer mode" box. Next click the "Load unpacked extension..." button and select the folder containing the git repo.
Let me know how it goes. It's possible that still might not work due to the way Chrome extensions are confined. In that case, I've got other options. It's just a bit annoying to work on since I can't test it.
The tool looks very promising but at each Github issue I select (following the video instructions) This tool tells me it doesn't look like a bug.
Any direction to where I can read what it needs to se things as a bug so this works like your video?
Thanks