Code Monkey home page Code Monkey logo

git-pear's People

Contributors

jish avatar salarkhan avatar supertopher avatar ziad-abdo avatar

Stargazers

 avatar  avatar  avatar

Watchers

 avatar

git-pear's Issues

Lingering users in the config

I signed out of pear and i still had a user in the local config.

I don't think we are scrubbing the user key
i ran
$ pear
and still had this in .git/config
screen shot 2014-08-28 at 11 52 16 am

Stretch goal: don't murder other pre-commit hooks

We should be able to append what we need to the pre-commit hook with our-pre-commit >> .git/pre-commit and i think we can remove it with ``our-pre-commit << .git/pre-commit`

I think we are gonna need an if clause to catch the shebang though... or we can just keep adding it forever as it is a comment but that seems stupid

Rewrite README

  • update screenshots
  • git log --full or whatever. whatever shows how the committers AND authors are switching
  • solo
  • GIT_API_TOKEN instructions

Uninstall

testing will require us to commit often and to want to remove the pieces that are under construction.

We should build the uninstall feature sooner than later to lower the burden of testing

Internal file invocation

Assuming the only commands the end user should ever need are 'pear', 'pear email email', and 'pear uninstall' --

Are we gonna have a file who's job it is to handle user input && invoke the respective files? Cause I was kinda confused about how file invocation within the application is supposed to work

Populate author name field with pair names/usernames

As referenced in #44, we should replace "Pear" with the Github usernames ( or real names ) of each pair member.

I imagine this will involve us making an API call to Github, so we should prob look into getting that API key as well.

Suggested ux for ending pair usage

typing just pear
should clear the user list and resume normal functionality to the program
this should be followed by the usage message

the usage message should explain that this happens if we implement this

Stop using exported variables

We should pass the path as argument instead of exporting PEAR_WORKING_DIR.
I think we can simply add it as another argument to uninstall and cycle... which i believe are the only two programs who need to know that location outside of the actual pair app

To quote salar:

"man, I'm super proud of what we've done here.

I would welcome all derogatory comments, since all they'll do is make this project sicker "

have at it plx @quackingduck @mweitzel

please note this is intended for a brew install so at the moment for testing as written the path must be amended to

PATH="$PATH:."

pear calls the command pear for functionality. If it's not in the path life is unhappy

it also probably needs an API key as i assume we will run into the same rate limiting problem we currently experience with iam weare

i don't think me or salar are opposed to some DBC branding in the read me or usage for shits and giggles. Wherever it goes i had fun writing this.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.