Let me make those changes quick in the background… Now all we have to do is make our changes. This command creates the branch and automagically switches you to it as shown below… Let’s create a branch called ‘fluentd-elasticsearch-kibanafix’ git checkout -b fluentd-elasticsearch-kibanafix So we’ll create our proposed changes in a new branch and add our commits (changes) to that. While I don’t think this is required, its certainly best practice so you aren’t working on code in the master branch directly. Now that we have a local copy of the code, we want to create a branch of the repo to make our changes in. This is done by using the Git ‘clone’ command… git clone The first step is to clone your new repo down onto your PC so you can work with the code. Notice that you’re looking at the same code, but it’s now under your name… When you hit ‘Fork’ Github will tell you that’s it’s copying the code…Īnd when it’s done, it will put you into your very own copy of the repo. Find the repo you want to fork and then click the ‘fork’ button as shown below… This is done most easily from the GitHub webpage. Forking essentially copies the code into your own repository. To start with, we’re going to ‘fork’ the Kubernetes repo. So I thought it would be good to document this PR so you can see the process and hopefully you’ll see that it’s really not that hard. Once your PR is submitted, people have a chance to review and comment on your suggested changes and if everything looks good, it will get pulled into the repository. ![]() ![]() A PR means you are submitting a request to ‘pull’ new code into the active repository. This is what’s called a ‘pull request’ or often just a ‘PR’. After some debugging, I think I found the issue so I’d like to suggest a change to the code to fix it. While playing around with the newest Kubernetes binaries I noticed a issue with the ‘fluentd-elasticsearch’ add-on in my lab. On the flip side, once you learn the basics it’s a very awesome tool for all kinds of revision tracking. And while it tries to help you from cutting yourself, it’s pretty easy to lose code you’ve worked on if you aren’t careful. ![]() It can be a frustrating tool to work with if you don’t know exactly what you’re doing. Being a network engineer, Git is not something that I used to use very frequently before I started messing around with Kubernetes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |