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

Add more command line arguments #5

Open
6 of 9 tasks
voiskiTest opened this issue Nov 10, 2017 · 1 comment
Open
6 of 9 tasks

Add more command line arguments #5

voiskiTest opened this issue Nov 10, 2017 · 1 comment

Comments

@voiskiTest
Copy link
Owner

Issue by IQAndreas
Friday Sep 13, 2013 at 01:53 GMT
Originally opened as IQAndreas/github-issues-import#5


  • Add option to pass config file location as a command line argument. (f0fdcc1)
  • Prevent any actual Python code from being able to be included in the config file (cd9f6fd)
  • Allow the username and password to be passed in as arguments (f0fdcc1)
  • Optionally, prompt the user for a username and password if none is provided in the config file. (06b6910)
  • Allow for the option of using API keys rather than entering your password and username (as was done in https://github.com/IQAndreas/ghup/tree/dev-generate-token).
  • Allow the option to import closed issues. I would recommend the flags --all, --open, --closed, or the default for the type of import.
  • Add --verbose options
  • Add --dry-run option (this would have made all this debugging easier)
  • Add --ignore-labels and --ignore-milestones (48917c8)
@voiskiTest
Copy link
Owner Author

Comment by IQAndreas
Sunday Sep 15, 2013 at 03:57 GMT


Old issue details (just changed this to a checklist in the main issue's body):

Pass config file location as argument

This allows the import script to be in one location, and the config file in another (for instance, in among the other repositories project files).

I may also need to prevent any "malicious" or "non-fitting" Python from being included in the file, but seeing as the same person who writes the config file in the same person who runs the script, I don't see this as being much of an issue.

Authorization

Perhaps allow the username and password to be passed in as arguments, or at least prompting the user for a username and password if none is provided in the config file (this is the most secure option, since it is never physically stored anywhere).

And allow for the option of using API keys rather than entering your password and username (as was done in https://github.com/IQAndreas/ghup/tree/dev-generate-token).

Allow the option to import closed issues

I'm not sure why this would be used, but it seems popular enough that several people have already incorporated such fixes into their own forks.

More arguments

  • Add --verbose options
  • Add --dry-run option (this would have made all this debugging easier)
  • Add --ignore-labels and --ignore-milestones

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