René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Rebase when pulling","articleBody":"When the local repo has unpushed commits and then doing a pull, it creates a merge commit, like this one:\r\n\r\n![screen shot 2017-01-27 at 8 04 03 pm](https://cloud.githubusercontent.com/assets/378023/22368898/48396e8a-e4cc-11e6-87f5-3c7540fe6916.png)\r\n\r\n![screen shot 2017-01-27 at 8 05 52 pm](https://cloud.githubusercontent.com/assets/378023/22368897/48392b5a-e4cc-11e6-9263-296d6612d0d6.png)\r\n\r\nShould it try to rebase instead? So that the history is kept clean? I think merge commits for PRs are fine, but when just pulling from the remote, it makes it a bit messy.\r\n\r\nOne day ™️ there could be a setting. Or like in Tower, a checkbox inline:\r\n\r\n![screen shot 2017-01-27 at 9 24 27 pm](https://cloud.githubusercontent.com/assets/378023/22370875/17666cda-e4d7-11e6-9af5-152389e5dd29.png)\r\n\r\nBut until then, use rebase as default?\r\n\r\n### Versions\r\n\r\nGitHub Package Version (`git --git-dir ~/.atom/packages/github/.git rev-parse head`): c93a942e1b2ead81371af74bf30db77e4a803675\r\n","author":{"url":"https://github.com/simurai","@type":"Person","name":"simurai"},"datePublished":"2017-01-27T12:30:01.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/493/github/issues/493"}