+ [2015-06-01T19:35:28Z] VxJasonxV Terabyte: link to a single wiki page consistently
+ [2015-06-01T20:04:56Z] euclio If I discover a bug that I want to submit a pull request for, should I submit an issue AND a pull request or just a PR?
+ [2015-06-01T20:06:39Z] VxJasonxV a pull request is just an issue with code
+ [2015-06-01T20:06:56Z] VxJasonxV unless the author asks you too, there's little reason to create both

message no. 96170

Posted by gfsh in #github at 2015-06-01T14:28:25Z

from the github web interface that is: "Able to merge. These branches can be automatically merged. "
+ [2015-06-02T07:46:28Z] VarunAgw Hi! I have a question regarding branches. Suppose I am working on a feature and want to commit frequently with meaningless changes that breaks existing code so I can revert back easily if needed. And then after I am done, I made my final important commit. Is it generally acceptable to do this or each commit in a branch have to be meaningful?
+ [2015-06-02T07:48:09Z] VarunAgw Meaningless commits can contain temporary files created to debug, lots of print and dump statements used for debugging, unnecessary file
+ [2015-06-02T07:52:54Z] Seveas VarunAgw: before merging (or submitting a PR) for such a branch, I would do an interactive rebase to clean up the useless crap
+ [2015-06-02T07:58:13Z] VxJasonxV interactive rebase to squash
+ [2015-06-02T07:59:06Z] VarunAgw Ah thanks! I completely forgot about this git feature