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

Handle 409 error (empty repository) #60

Merged
merged 1 commit into from May 17, 2014

Conversation

Projects
None yet
3 participants
@alexbeletsky
Contributor

alexbeletsky commented May 16, 2014

In case you create new repository, or browsing empty one it shows ugly Error: 409 error. Added handler to fail more gracefully (+ my editor removed some empty spaces :) )

@buunguyen

This comment has been minimized.

Show comment
Hide comment
@buunguyen

buunguyen May 16, 2014

What's being changed here? Doesn't seem like white-spacing cleaning.

buunguyen commented on src/inject.js in 1e8e4ef May 16, 2014

What's being changed here? Doesn't seem like white-spacing cleaning.

This comment has been minimized.

Show comment
Hide comment
@alexbeletsky

alexbeletsky May 17, 2014

Owner

It looks a bit odd, but in fact it's nothing changed there.. all names are still in place.

Owner

alexbeletsky replied May 17, 2014

It looks a bit odd, but in fact it's nothing changed there.. all names are still in place.

@Glaived

This comment has been minimized.

Show comment
Hide comment
@Glaived

Glaived May 17, 2014

#60 (comment) +1 with Firefox

@buunguyen look line 165

Glaived commented May 17, 2014

#60 (comment) +1 with Firefox

@buunguyen look line 165

buunguyen added a commit that referenced this pull request May 17, 2014

Merge pull request #60 from alexanderbeletsky/handle-409
Handle 409 error (empty repository)

@buunguyen buunguyen merged commit 45e3fcc into buunguyen:master May 17, 2014

@buunguyen buunguyen added the bug label May 19, 2014

@buunguyen buunguyen changed the title from handle 409 error to Handle 409 error (empty repository) May 19, 2014

@buunguyen buunguyen added this to the 1.2.0 milestone May 19, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment