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.

Sign up for GitHub

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

chore(docs): add note about bypassing SSL errors #104

Merged
merged 1 commit into from
Dec 8, 2023
Merged

chore(docs): add note about bypassing SSL errors #104

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,3 +143,12 @@ gh migrate-project import \
Near the start of the import, the tool will ask you to manually set up your options for the "Status" field. It will explain exactly what to do, and will validate that you've correctly copied the options from your migration source.

Once you've set up the "Status" field, your project will be imported. Watch out for `warn` lines in the logs, which will let you know about data which hasn't been imported.

### Troubleshooting

If you run into SSL connection errors and you are unable to set your proxy settings with the `--proxy-url` parameter, you can set the `NODE_TLS_REJECT_UNAUTHORIZED=0` environment variable to bypass:

```
export NODE_TLS_REJECT_UNAUTHORIZED=0 # setting an environment variable in bash
$Env:NODE_TLS_REJECT_UNAUTHORIZED = 0 # setting an environment variable in PowerShell
```