search

rolly32 / rolly

Automatically exported from code.google.com/p/support-tools
0 stars 0 forks source link

Issue labels not created when you don't own the GitHub repo #95

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
It looks like issue labels aren't created when the person running the GitHub 
issue export script does not own the repo. See:

https://github.com/firebug/firebug/issues/
vs.
https://github.com/chrsmith/firebug-issue-export-tool-testing/issues

Original issue reported on code.google.com by chrsm...@google.com on 4 Jun 2015 at 3:56

GoogleCodeExporter commented 9 years ago 
From the GitHub API docs:

Only users with "push" access can set labels for new issues. See:
https://developer.github.com/v3/issues/#create-an-issue

So in the future, you need to grant explicit push access to the repo before 
running the tool (when running as a different user). However, for issues that 
have already been created it looks like a separate "add missing labels" step is 
necessary.

Original comment by chrsm...@google.com on 4 Jun 2015 at 4:28

GoogleCodeExporter commented 9 years ago 
The exporter user is added as a collaborator before running the export (and 
removed afterward). Is being a collaborator not enough?

Original comment by jasonhall@google.com on 4 Jun 2015 at 4:33

GoogleCodeExporter commented 9 years ago 
Yes, it is enough for the Google Code to GitHub issue exporter. However, for 
the stand-alone tools you need to manually do it.

Original comment by chrsm...@google.com on 4 Jun 2015 at 4:46

rolly32 commented 9 years ago

Yes, it is enough for the Google Code to GitHub issue exporter. However, for the stand-alone tools you need to manually do it. Original comment by chrsm...@google.com on 4 Jun 2015 at 4:46

rolly32 commented 9 years ago

Yes, it is enough for the Google Code to GitHub issue exporter. However, for the stand-alone tools you need to manually do it. Original comment by chrsm...@google.com on 4 Jun 2015 at 4:46