When working with Git (or any version control system) most developers tend to commit all the changes in a given file. What if you wanted to only commit part of the file? This situation can occur in a few situations, such as:
- Code not ready to be committed
- Working on two tickets at once and want separate commits for each set of work
TODOcomments that you don’t want in the codebase
Git has a feature called interactive staging which lets you select specific lines of code you want staged (and then committed). The demo below highlights this using Visual Studio Code‘s (VSCode) Git tools.
In my current file I have the following:
We can divide up the “new code” into two sections. The first
select statement should be committed but the second statement (staring with
-- TODO mdsouza) should not be committed.
If the file needs to be committed without interactive staging a few options exist:
- Commit everything
- Cut out the sections I don’t want in and paste them back in after commit
- Copy file (as a backup), remove sections I don’t want, commit, restore backup
Neither of these options will lead to good results and take additional time. Using VSCode you can do interactive staging in multiple ways. The following shows how to stage specific lines.
A few things to note from the demo:
- Once staged,
test.sqlwas still marked as having both changes and staged changes
- Only selected lines were staged (then committed)
Since finding out about interactive staging I’ve been using it to restrict what goes into each commit. It’s allowed me to keep my commits more concise along with not having to commit work that isn’t ready for others (ex: personal