Labs are hands-on coding projects that you build along with Tonya as she explains the code, concepts, and thought processes behind it. You can use the labs to further your code knowledge or to use right in your projects. Each lab ties into the Docx to ensure you have the information you need.
Each lab is designed to further your understanding and mastery of code. You learn more about how to think about its construction, quality, maintainability, programmatic and logical thought, and problem-solving. While you may be building a specific thing, Tonya presents the why of it to make it adaptable far beyond that specific implementation, thereby giving you the means to make it your own, in any context.
Let’s tame git. Let’s create a rich set of commands and shortcuts that make sense and are intuitive. Let’s build a set of scripts that are callable by a single command, such as `git uncommit` or `git rollback`, i.e. commands that wrap up repetitive tasks and automate them via a single command. In this hands-on coding lab, you’ll build a rich collection of these commands via git aliases and bash scripting to git you more productive.
There are times when you are working on a change and then realize that you’ve gone in the wrong direction. At that point, you want to rollback your project back to the last commit, i.e. meaning you want to delete all of the changes and return your codebase back to the last commit. There are multiple steps to do this task as you need to delete everything in the staging and working areas. Let’s build an alias.
Recall from Simply Git and Git Contributing how to commit changes. It is a two-step process of adding the changes from working into staging and then running git commit to move from staging into the storage (commit) area. Git gives you a way to combine those steps into one step. Typically, my workflow is: Commit the changes Pop open the editor Add my commit message Clear off the command line console View the status display View the log That’s a lot of steps to type over and over again. Let’s build a complex alias to give us one command git […]
Imagine that you are working along on a change and then decide you need to rename the branch. Git gives you an option to move a branch to a new branch. But like most git commands, it’s not intuitive or rememberable. Let’s build an alias.
In Git Contributing, you learned how to create and checkout a new branch. I don’t know about you, but I find the command and option confusing. Let’s build an alias.
In the last episode, I warned you that fixing your last commit message when you have changes in the working or staging area is problematic. We can solve that problem by staging all of the changes before we fix the message and then restoring them after we’re done. Let’s build an alias.
You know that you can use git status to view what is currently in the working and staging areas. In this episode, let’s make an alias for a less verbose status.
What if you don’t want to unstage all of the changes; rather, you just want to unstage a specific change. Running git status tells you how to do it. But again the command and its options is not intuitive or rememberable. Let’s build a complex alias that: Processes the optional parameter when one is given with the command. Or sets a default value when one is not passed with the command.
Often times, we type a series of commands over and over again. Is there a way to group these commands into one complex alias? Yes, we can leverage the shell and gain access to the full suite of Unix commands via scripting. In this episode, let’s discover the bang operator and anonymous function.
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.
Know the Code develops and empowers professional WordPress developers, like you. We help you to grow, innovate, and prosper.