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

feat: add defaults for the import command's --input-path and --repository-mappings-path arguments #105

Merged
merged 1 commit into from
Dec 8, 2023

Conversation

joshjohanning
Copy link
Contributor

@joshjohanning joshjohanning commented Dec 8, 2023

For importing, setting defaults for the --input-path and --repository-mappings-path parameters.

I would imagine most people running this are going to run the export in a folder, update the repo mappings, and then run the import. Setting defaults saves some typing/copy+pasting 😄

And also, the gh migrate-project --help already mentioned defaults (I realize it was mentioning the default for the export command, but we might as well default it for the import command too.

--input-path <input_path> The path to the exported project data. This will be the --project-output-path argument passed to the export command, which defaults to project.json.
--repository-mappings-path <repository_mappings_path> The path to your completed repository mappings file. This will be the --repository-mappings-output-path argument passed to the export command, which defaults to repository-mappings.csv.

@timrogers timrogers changed the title feat: default import file paths feat: add defaults for the import command's --input-path and --repository-mappings-path arguments Dec 8, 2023
Copy link
Owner

@timrogers timrogers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😍 This is an obviously sensible change, and something I should have done! Thanks for the suggestion.

@timrogers timrogers merged commit 8e86bb8 into timrogers:main Dec 8, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants