One of the first things I do after a new installation of myt OS of choice Ubuntu, is to clone all my repositories from GitHub. This way, I have all my code and configuration files available locally, and I can start working on them right away instead of loading them each time I start working on any project.

My recent days were marked by the biennial (as in every two years) prematurely (I’ll explain that in a later post) installation of a new Ubuntu LTS (long term support) version.

Pushing a new branch to a repository’s remote often requires two attempts by the scatterbrained developer, but there is help in push.autoSetupRemote.

Workspaces are a great feature in VSCode. But they have their issues. For instance starting VSCode in a folder will not automatically load the workspace file. This can be annoying if you have a workspace file in the folder and you want to open it directly.

The .gitignore file in a Git repository serves as a configuration file that specifies files and directories that Git should — as the name implies — ignore. When Git encounters a file or directory listed in .gitignore, it automatically excludes them from being tracked, preventing them from showing up in commands like git status and git add.

GitHub recently introduced an innovative feature for Markdown documents that allows users to highlight “Note”, “Warning”, and other notification blocks more effectively. An enhancement useful for developers who want to draw attention to important information in their documentation or discussions.