Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wiki page documenting user_file_path #23

Open
GoogleCodeExporter opened this issue Oct 1, 2015 · 2 comments
Open

Wiki page documenting user_file_path #23

GoogleCodeExporter opened this issue Oct 1, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

I am trying to import issues in bitbucket. All users get replaced with the 
provided default username. I saw that there is an "user_file_path" option to 
give a mapping. But I found no documentation what syntax this file should have. 
Please provide a wiki page explaining this.

Original issue reported on code.google.com by crazy4ch...@gmail.com on 13 Mar 2015 at 9:17

@GoogleCodeExporter
Copy link
Author

Original comment by jasonhall@google.com on 16 Mar 2015 at 8:51

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

@GoogleCodeExporter
Copy link
Author

I found the following documentation in the program for exporting the issues to 
GitHub:

  4. (Optional) If this option is skipped all issues will be assigned to the
     owner of the repo.  Make a file that contains a mapping from the Google
     Code email address to the GitHub username for each user you wish to assign
     issues too.  The file should be newline seperated with one user per line.
     The email address and username should be colon (':') seperated. For example
     a file may look like this:
       <Google Code Email>:<GitHub Username>
       myemail@gmail.com:coolperson
       otheruser@gmail.com:userother

This information is also missing from the wiki.

Original comment by andres.s...@gmail.com on 26 Mar 2015 at 4:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant