In Simply Git, you learned how to uncommit the last commit, moving the changes back into your working area. The command is not intuitive and, therefore, not rememberable. Let’s build an alias.
What if you want to delete or rename an alias? How do you do that? Here, let me show you.
Let’s walk through what happens when your contribution is approved and then merged into the project. Note: This process is handled for you by the project’s review team and whomever is authorized to add (merge) your contribution to the project. But let’s walk through it together.
Developers contribute. We work on teams and/or give our time to open source projects. In order to contribute, you need to be comfortable with git, GitHub, and the workflow process. In this hands-on coding, you will learn how to wire everything up, use branching, keep everything in sync and up-to-date, handle merge or commit issues, create issues, create pull requests (PR), and more. Let’s git you contributing.
Let’s stop here and explore how the work you just did in the change/license branch is separate and isolated from the develop branch. It’s important for you to understand why you want to do your work in a branch, i.e. whether working on your own project or on a team.
Ever wondering how git actually works? It’s a tool that you use every day. How are the commit hashes being generated? How does it keep track of everything? In this hands-on coding lab, you will dive into git bits by taking a look inside of git’s internals.
Version control is an essential part of any developer’s workflow. You know that. But it’s overwhelming and downright confusing to get started. Let’s cut through the technical jargon, workflows, and confusion. In this hands-on coding lab, you will simply learn git essential commands, with no fluff, just barebones git to get you started.
What happens if you made a commit and then realized, whoops, I didn’t want to commit those changes? How can you “uncommit” a commit? Let’s do it together.
There are times when you are working on changes and then realize, “Whoops, I’m going in the wrong direction.” When that happens, you want to ability to rollback those changes (or some of them) to the previous commit state. How do you do that? Git gives you a command to remove one, some, or all of the changed tracked files. But what if you have new directories and/or files? How do you remove those? Let’s dig into this topic in this episode.
Before we start customizing the theme, we want to store away a snapshot of the original theme. Why? At this point, all we did was git the Twenty Seventeen theme into version control. Nothing has been stored (committed). Therefore, ALL of the theme’s files are new to git. That means it sees all of the files as changed. Okay, but when you go to make your first customizations, you will want to know what was customized. To isolate those changes, you first need to commit the original theme. Let’s talk through this in this episode.