Issue #25 (Working with Git Repos)10/12/22
|
|
|
Get a weekly dose of tools, articles, and other resources covering remote work, productivity, career well-being, and lots more.
|
|
|
|
As I've mentioned previously, Git features are integrated directly inside VS Code in the Source Control sidebar panel. All the basic Git features are easily accessible in that panel, along with more advanced source control features in the "Views and More Actions..." menu (three dots).
Along with those basic Git features, you have ways to customize how VS Code works with your Git repositories. If you
open your Settings UI and type "git" you'll see different ways to customize how VS Code interacts with your repositories.
Some notable settings you might consider adjusting include
setting Autofetch to "true" (it's false by default) and assigning
a custom Autofetch Period, or duration between autofetch requests:
This means if there are any changes to the remote repository, VS Code will automatically fetch those changes for me at the specified interval. These might also be settings you'll want to adjust on a project by project basis. So you can use VS Code's Workspaces feature to define custom autofetching for specific projects, and leave the defaults in place for others.
You can also define
when repositories are automatically detected and there are a number of
branch-related settings such as automatically adding a custom prefix to all newly created branches:
Again, these are settings that may be most useful when applied to specific repositories using VS Code Workspaces, not necessarily global settings that apply everywhere.
Finally, you might want to change the number of prompts you get when working with Git in VS Code:
Most of these prompts are probably useful to keep, but if you want to improve your workflow speed by avoiding alerts that you don't require, you might consider turning one or more of these off.
