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

Make it easier to trouble-shoot a failure to connect to bitbucket #10

Merged
merged 1 commit into from Aug 25, 2014

Conversation

Projects
None yet
2 participants
@c-w
Copy link
Contributor

commented Aug 22, 2014

Unlike on Github, the repository name on Bitbucket is case sensitive. This
gotcha is a bit counter-intuitive and therefore can lead to some head-scratching
as to why the migration script is failing. Improving the exception message makes
it easier to figure out what is going wrong.

Easier to debug connect-to-bitbucket failure
Unlike on Github, the repository name on Bitbucket is case sensitive. This
gotcha is a bit counter-intuitive and therefore can lead to some head-scratching
as to why the migration script is failing. Improving the exception message makes
it easier to figure out what is going wrong.

vbabiy added a commit that referenced this pull request Aug 25, 2014

Merge pull request #10 from c-w/master
Make it easier to trouble-shoot a failure to connect to bitbucket

@vbabiy vbabiy merged commit 470afe0 into jeffwidman:master Aug 25, 2014

haysclark pushed a commit to haysclark/bitbucket_issue_migration that referenced this pull request Dec 9, 2014

Merge pull request jeffwidman#10 from c-w/master
Make it easier to trouble-shoot a failure to connect to bitbucket
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.