+[2015-06-01T19:35:28Z]VxJasonxVTerabyte: link to a single wiki page consistently +[2015-06-01T19:35:55Z]Terabytemmm +[2015-06-01T20:04:56Z]euclioIf 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]VxJasonxVa pull request is just an issue with code +[2015-06-01T20:06:56Z]VxJasonxVunless the author asks you too, there's little reason to create both
can I automatically merge changes made to a repository I forked at an earlier date?
+[2015-06-02T07:46:28Z]VarunAgwHi! 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]VarunAgwMeaningless commits can contain temporary files created to debug, lots of print and dump statements used for debugging, unnecessary file +[2015-06-02T07:52:54Z]SeveasVarunAgw: 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]VxJasonxVinteractive rebase to squash +[2015-06-02T07:59:06Z]VarunAgwAh thanks! I completely forgot about this git feature