-
Notifications
You must be signed in to change notification settings - Fork 107
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
[WIP] bin: custom git commands #98
Conversation
Codecov Report
@@ Coverage Diff @@
## master #98 +/- ##
=======================================
Coverage 98.17% 98.17%
=======================================
Files 14 14
Lines 492 492
=======================================
Hits 483 483
Misses 9 9 Continue to review full report at Codecov.
|
|
||
echo " | ||
1) To land single a commit: | ||
git node just <PRID> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@joyeecheung just want to know am i mistaken or this should be git-node
instead of git node
as we have git-node
in package.json
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The git custom commands work like this: if you have an executable named "git-*" on your path, the it will be run when you do "git *"
@joyeecheung this PR looks great! Great Work. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks way too cool.
Just setting my review to "comment" while you finish your wip.
Oh....I know why my pushed commits didn't show up here now, it's being merged from the branch here now that this repo has been transferred.....I'll close this and open another one from my fork. |
This implements a custom git command
git node
that automate the landing process.Still a WIP, trying to port everything into node scripts..