While you were working, other people were working, too. “This branch is n commits behind (source-repo).” Then, when you’re ready to work, you notice the message on your fork. You spend some time examining the files and interpreting the code. You create a fork (an online copy) of a repository and a clone (a local copy on disk) of your fork. If this solution works for you, tweet your thanks to Steven. My utmost thanks to PowerShell MVP and Principal Engineer – Community Engineering for Chef, Steven Murawski for showing me the solution and letting me try it by myself (twice) while he was standing nearby in case of disaster. I just discovered a solution to one of the problems I encounter frequently, so I want to share it with you. Worst of all, because most people memorize a command sequence without fully understanding how it works, when something goes wrong, it’s almost impossible to troubleshoot. ![]() To use it, you have to forget the actual meaning of words in English, or even their technical meaning, and use them as though they are arbitrary strings. Its misleading language excludes users, rather than welcoming them. ![]() In fact, I dislike it, because it’s confusing by design. Like almost everyone in the DevOps world, I use GitHub, not because I like it, but because everyone uses it.
0 Comments
Leave a Reply. |