-
Notifications
You must be signed in to change notification settings - Fork 148
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
Add tests/specs #88
Comments
Not strong ones, but this isn't a very maintained project in the first place, and is less relevant now that Git 2.0 has better push behaviour. |
I'm curious. How does the new push behavior in Git 2.0 make the smart pulling that git-up provides less relevant? |
Prior to Git 2.0, Now that I'd still like to find the time for a grand rewrite, for several reasons:
...but these days I have so little time. |
Adding my two cents as a user. I've been a regular user of For me, those "other benefits" are actually the main reason I like to use it. I can understand that in the general case that is not particularly valuable. That said, it feels like the grand rewrite will probably never happen, which is not a problem, so I only ask the maintainers that those behaviors not be lost if an attempt to do the rewrite stumbles. In summary, |
Concerning tests: I have an integration test suite in my Python port. If |
I'm getting ready to write some tests for git-up. Any objections to RSpec?
The text was updated successfully, but these errors were encountered: