-
Notifications
You must be signed in to change notification settings - Fork 161
Add the Notification API #147
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
Conversation
Oh, you don't need to create a new PR to change this- you can simply "git push origin [branch] -f" and github is smart enough to update the code but keep the notes. I did this first time I committed here #14 :) To quote Sébastien when I did it: "this is better than reopening a new PR because comments are kept and correlated with the new commits for lines that have not changed." |
doh! .. sorry I did a re-checkout. I also forgot to update the import in the example which i have done now. How do I reissue the pull request with the fix? |
👍 got it before I finished typing. The only other issue is you're PR'ing from master (should have caught this earlier, blah) onto master which causes issues if we need to go through history. The PR should be a single commit for this, in a branch, say |
The way to do this is first wind back your working directory two commits, but keep your changes. |
bleh. isaacs/github#18 seems it's not possible. once you have a |
Ok thanks for your help 👍 |
np. my first few PR's were a total car accident ;) |
I have used this line twice already.. lol :) |
;) thanks for the PR 👍 |
No description provided.