search

calavera / ey_cli

Alternative CLI for Engine Yard Cloud
Other
11 stars 5 forks source link

Make git utils use cli git instead of grit #9

Closed cwgem closed 13 years ago

cwgem commented 13 years ago

Currently the only way git is being used is to check for a .git directory (which is done with a simple directory existence check) and obtaining the repo's remote repository. Plan of action:

  1. Use git cli to do a sanity check on the repo. This will prevent the case where .git exists but the repository is somehow corrupted enough to where git can't work with it.
  2. Use git config to pull the origin repository URL

Currently working on this in another branch. I'll post the commit URL here once it's done and merge it into master if it looks okay. Hopefully it will get apps_spec.rb all green in the process. If not then that will be the next task!

drnic commented 13 years ago

Are we all over investing time in this? ;)

Cheers Nic

http://engineyard.com http://drnicwilliams.com +1 (415) 322 9556

Engine Yard: Successful Rails Apps through Orchestration

On Oct 4, 2011, at 7:01 PM, Chris Whitereply@reply.github.com wrote:

Currently the only way git is being used is to check for a .git directory (which is done with a simple directory existence check) and obtaining the repo's remote repository. Plan of action:

  1. Use git cli to do a sanity check on the repo. This will prevent the case where .git exists but the repository is somehow corrupted enough to where git can't work with it.
  2. Use git config to pull the origin repository URL

Currently working on this in another branch. I'll post the commit URL here once it's done and merge it into master if it looks okay.

Reply to this email directly or view it on GitHub: https://github.com/calavera/ey_cli/issues/9

drnic commented 13 years ago

I say that without knowing the plans nor state of this. I know nothing.

Cheers Nic

http://engineyard.com http://drnicwilliams.com +1 (415) 322 9556

Engine Yard: Successful Rails Apps through Orchestration

On Oct 4, 2011, at 7:01 PM, Chris Whitereply@reply.github.com wrote:

Currently the only way git is being used is to check for a .git directory (which is done with a simple directory existence check) and obtaining the repo's remote repository. Plan of action:

  1. Use git cli to do a sanity check on the repo. This will prevent the case where .git exists but the repository is somehow corrupted enough to where git can't work with it.
  2. Use git config to pull the origin repository URL

Currently working on this in another branch. I'll post the commit URL here once it's done and merge it into master if it looks okay.

Reply to this email directly or view it on GitHub: https://github.com/calavera/ey_cli/issues/9

calavera commented 13 years ago

@drnic, this is what I do in my "compiling time" http://xkcd.com/303/ I.e: waiting resin releases, awsm tests pass...

Check the list of commands to see what has been done for now:

https://github.com/calavera/ey_cli/tree/master/lib/ey_cli/commands

btw, don't kidnap the threads!! :P

@cwgem, I'd use git cli, something like this just works:

git config -f .git/config --get 'remote.origin.url'
calavera commented 13 years ago

Fixed.