Skip to content

Conversation

@tspascoal
Copy link
Contributor

Git Bash has an automatic mapping of URLs to cather for the difference between windows/unix paths.

So API calls that starts with a slash get transformed to a windows path and commands fail to run.

eg calling gh api /user the called URL is /C:/Program%20Files/Git/user

Git Bash has an automatic mapping of URLs to cather for the difference between windows/unix paths.

So API calls that starts with a slash get transformed to a windows path and commands fail to run.
@andyfeller
Copy link
Owner

Thanks @tspascoal! I've actually run into this before when I've occasionally worked on my personal laptop in cli/cli#6415.

Given there have been a few changes since this PR opened, let me follow up and do the right thing 👍

@andyfeller
Copy link
Owner

@tspascoal : I've made some substantial linting changes to the gh-repos-export extension since this pull request was created. After reviewing your changes, they seem simple enough, however I want to ask what made for getting these changes updated for review:

  1. Close pull request, update your fork based on released changes, and resubmit
  2. Close pull request, I can open pull request

Let me know what makes sense so we can ensure this works for Git Bash users 🙇

@andyfeller andyfeller linked an issue Aug 3, 2023 that may be closed by this pull request
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.

Update gh api calls in order to support Git Bash

2 participants