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

Ensure 1:1 mapping between tasks and git commands #44

Closed
12 tasks done
rubenv opened this issue Mar 28, 2014 · 1 comment
Closed
12 tasks done

Ensure 1:1 mapping between tasks and git commands #44

rubenv opened this issue Mar 28, 2014 · 1 comment

Comments

@rubenv
Copy link
Owner

rubenv commented Mar 28, 2014

Tasks to check:

  • archive
  • checkout
  • clean
  • clone
  • commit
  • merge
  • pull
  • push
  • rebase
  • reset
  • stash
  • tag

This is related to the discussion in #38. Each command needs to be checked before we can release the first 0.3 release.

Things to look out for:

  • Does the grunt task do the same thing as the git command?
  • Do the options work as the git task?

Ideally you'd only need to know how to use the git command: converting that command to a grunt configuration should be trivial.

Anyone who wants: feel free to jump in!

@rubenv
Copy link
Owner Author

rubenv commented Sep 3, 2014

@dylancwood I pulled add out of commit. This pretty much opens the door to release a new major version (I'm thinking of calling it 1.0.0). Anything else should include?

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

No branches or pull requests

1 participant