René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Thoughts about --auto-pull --auto-push flags?","articleBody":"Hey ;D\r\n\r\nI'm a \"heavy\" user of gitcheck... and I love it ;D\r\n\r\nI work on multiple computers everyday - my laptop, my desktop, the company desktop,\r\nand every once in a while, a remote server. Since I'm working at same projects\r\nin all of them I constantly have to push all my changes and pull as well.\r\n\r\nSo, I run ```gitcheck --remote --quiet``` just to discover the repos that \r\nhave changed and after that I need go to every repo and push/pull accordingly.\r\nThat's sucks a lot... I mean the gitcheck is doing its job great but yet I \r\nneed do a lot of manual stuff :/\r\n\r\nWith that in mind, I implemented a crude --auto-push and --auto-pull flags.\r\nThey work like that:\r\n\r\n1. Check if repo has something to pull.\r\n2. Check if repo has something to push.\r\n3. If only pull is true - make a pull.\r\n4. If only push is true - make a push.\r\n\r\nYep, that's it... nothing fancy at this stage. But something interesting can\r\nbe worked out... like: \r\n\r\n* try to pull first and if no merge conflicts occurs then push.\r\n* if a merge conflict happened revert the merge.\r\n* etc...\r\n\r\nI don't know if it's very specific to my work flow, or other ppl might \r\nhave similar \"issues\" with that - and if do you want something like that\r\nin gitcheck at first place.\r\n\r\nIf it's something that sounds good to you I can refine my work in about 3,4 days\r\nand submit a pull request ;D\r\n\r\nTell me what you think about it!\r\n\r\nCheers and thanks for gitcheck!\r\n","author":{"url":"https://github.com/saturnodigital","@type":"Person","name":"saturnodigital"},"datePublished":"2017-09-26T01:28:04.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/41/gitcheck/issues/41"}