Git & Development Tricks: Github, Gitlab and more

When I started to use Git, I could actually start see my progress and build upon my previous effort.

This is a recap of the best GIT related tricks I have so far.

Github

1. Use vscode on the cloud with: https://github.com/codespaces/

2. GISTS are a great way to share code: https://jalcocert.github.io/JAlcocerT/github-gists/

sudo apt install git #you need GIT first
#git remote -v

You will also need:

git config --global user.name "JAlcocerT"
git config --global user.email "youremail@example.com"

See active branch and latest commits:

#git branch
git log --oneline -n 10

Creating Releases

And given a project, you can get the latest Github release as per:

Github Actions

Using github CI/CD can be very helpful:

Chat with Data

Other LangChain use cases

GHA 101 Post

How to get the most out of Github Actions

Github Actions MultiArch Images:

1. With QEMU: as explained here
2. ARM86 native builds with GHA

Since this year, 2025, we can also build ARM64 images natively with GHActions!

Github Pages

https://jalcocert.github.io/JAlcocerT/how-to-use-github-pages/

Gitlab

Not everything is Github.

There are very cool projects on Gitlab as well.

You can start by adding the Gitlab extension to sync your repos:

code --install-extension gitlab.gitlab-workflow

Definitely use the extension GitLab Workflow VS Code Extension.

Authenticate with OAuth.

#sudo snap install gitlab-cli
sudo snap install glab

glab auth login #you will need https://gitlab.com/-/user_settings/personal_access_tokens?page=1
glab mr list
#glab mr diff 25

VSCode

You can install vscode in Ubuntu with flatpak:

flatpak install flathub com.visualstudio.code #https://flathub.org/apps/com.visualstudio.code
flatpak list --app
#flatpak list --columns=all

#flatpak uninstall com.visualstudio.code

Or with snap, which I would recommend:

sudo snap install code --classic

There are some cool extensions to help you create.

• Name: Dev Containers
  • Id: ms-vscode-remote.remote-containers
  • VS Marketplace Link

Remember that there are many cool extensions: https://marketplace.visualstudio.com/VSCode

And that they can be installed programatically:

codium --install-extension gitlab.gitlab-workflow
#code --install-extension gitlab.gitlab-workflow

Remote Development

I was discovering some vscode triks here.

The most important steps?

SSH Dev

We need this extension: https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.vscode-remote-extensionpack

ext install ms-vscode-remote.vscode-remote-extensionpack #do this one inside VSCode with CTRL+SHIFT+P
#code --install-extension ms-vscode-remote.vscode-remote-extensionpack #or this one from the terminal

Then, do CTRL SHIFT P and write: connect to host

This video summarizes it very well

When you are done, you will get the possibility to connect confortably:

Container Dev

ext install ms-vscode-remote.remote-containers #do this one inside VSCode with CTRL+SHIFT+P
#code --install-extension ms-vscode-remote.remote-containers #or this one from the terminal

sudo usermod -aG docker jalcocert
groups jalcocert

#sudo groupadd docker
#sudo usermod -aG docker $USER

This can be very useful to do Jekyll web dev as seen here

Generally, to develop inside a container…you will need one.

More VSCode extensions

#code --install-extension gitlab.gitlab-workflow

#https://marketplace.visualstudio.com/items?itemName=unifiedjs.vscode-mdx
ext install unifiedjs.vscode-mdx

#https://marketplace.visualstudio.com/items?itemName=eliostruyf.vscode-front-matter
ext install eliostruyf.vscode-front-matter
#code --install-extension eliostruyf.vscode-front-matter

#docker #https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker
ext install ms-azuretools.vscode-docker
#https://marketplace.windsurf.com/extension/ms-azuretools/vscode-docker

#MDX #https://open-vsx.org/vscode/item?itemName=unifiedjs.vscode-mdx
ext install unifiedjs.vscode-mdx

#github actions https://marketplace.visualstudio.com/items?itemName=github.vscode-github-actions
ext install GitHub.vscode-github-actions #
#code --install-extension GitHub.vscode-github-actions

#slidev
ext install antfu.slidev
#code --install-extension antfu.slidev #or this one from the terminal

#python
ext install ms-python.python #https://marketplace.visualstudio.com/items?itemName=ms-python.python

#https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens
ext install eamodio.gitlens
#code --install-extension eamodio.gitlens #or this one from the terminal

#yaml https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml


#makefile #https://marketplace.visualstudio.com/items?itemName=ms-vscode.makefile-tools
ext install ms-vscode.makefile-tools

Diagrams/Wireframes…

#gemini assistant https://marketplace.visualstudio.com/items?itemName=Google.geminicodeassist

#jupyter https://marketplace.visualstudio.com/items/?itemName=ms-toolsai.jupyter

#excalidraw https://marketplace.visualstudio.com/items?itemName=pomdtr.excalidraw-editor
ext install pomdtr.excalidraw-editor

#formatter #https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode
ext install esbenp.prettier-vscode

Outro

Lately, a colleague mentioned to me about: https://lovable.dev/

Lovable is an AI software engineer, which enables anyone to build for the web. Simply chat to instantly build websites and web apps, with no technical knowledge needed.

It seems this is called vibe coding!

It requires a signup, yet, they provide a free tier.

Definitely have to take a look to suck tools and also to the open/local ones.

Use VSCodium via container:

Weekly Planning

A proactive approach to planning, information sharing, and continuous learning:

================= WK1234 Y25 | Sprint 123ab =================

Sprint Goal: [Clearly state the overarching goal of the sprint]

FAQ

MonoRepos and more

What is a Mono repo?

At its core, a monorepo is a single repository that contains code for many different projects, libraries, and applications. Instead of having separate repositories for each part of your codebase, everything lives together in one big happy family.

Think of it like organizing all your important documents into one well-structured filing cabinet instead of scattering them across multiple folders and drawers.

What are the Alternatives?

The primary alternative to a monorepo is a multirepo (also sometimes called a polyrepo).

In a multirepo setup, each project, library, or application has its own distinct repository.

This has been the more traditional approach for a long time.

Pros and Cons:

Let’s weigh the advantages and disadvantages of each approach:

Monorepo:

Pros:

• Simplified Dependencies: Managing dependencies across projects becomes much easier. You can often have a single version of a library used by multiple projects, reducing inconsistencies and potential conflicts.
• Code Sharing and Reuse: It’s simpler to share code and components between different parts of your organization. Changes to shared libraries are immediately available to all dependent projects.
• Atomic Commits: You can make changes that span multiple projects in a single commit, ensuring consistency across related code modifications.
• Easier Refactoring: Large-scale refactoring across multiple projects is more straightforward since all the code is in one place.
• Centralized Build and Deployment: You can often set up a unified build and deployment pipeline for all projects in the monorepo.
• Improved Visibility: It’s easier to see how different parts of the system interact and understand the overall codebase.
• Streamlined Onboarding: New team members have a single place to clone the entire codebase, making it easier to get started (though the size can be a factor).

Cons:

• Size and Scalability: As the monorepo grows, it can become very large, potentially impacting clone times, build times, and IDE performance.
• Build Complexity: While centralization can be a pro, configuring and optimizing the build process for a diverse set of projects can become complex.
• Permissions and Access Control: Managing permissions and ensuring that teams only have access to the relevant parts of the codebase can be challenging.
• Tooling Maturity: While tooling for monorepos has improved significantly, it might not be as mature or widely adopted as tooling for multirepos in some areas.
• Impact of Changes: A breaking change in a shared library can potentially affect many different projects within the monorepo.
• Perceived Complexity: Some developers might find the sheer size and scope of a monorepo intimidating initially.

Multirepo:

Pros:

• Clear Boundaries and Ownership: Each project has its own repository, making ownership and responsibilities clear.
• Smaller and Faster Clones: Individual repositories are typically smaller, leading to faster clone times and less disk space usage.
• Independent Builds and Deployments: Projects can often be built and deployed independently, reducing the risk of one project’s issues affecting others.
• Technology Diversity: Teams can choose the best technologies and tools for their specific project without impacting others.
• Mature Tooling: The tooling and workflows around multirepos are generally well-established and widely understood.
• Improved Isolation: Changes in one repository are less likely to have unintended consequences on other projects.

Cons:

• Dependency Management: Managing dependencies across multiple repositories can be complex, often leading to version inconsistencies and integration challenges.
• Code Sharing Challenges: Sharing code between repositories can be cumbersome, often requiring the creation and maintenance of separate libraries or packages.
• Coordination Overhead: Making changes that span multiple projects requires more coordination and can be more prone to errors.
• Refactoring Difficulties: Large-scale refactoring across multiple repositories is significantly more challenging.
• Inconsistent Development Experience: Teams working on different repositories might have different build processes, testing strategies, and deployment workflows.
• Reduced Visibility: It can be harder to get a holistic view of the entire system and how different parts interact.

Which one is right for you?

The choice between a monorepo and a multirepo depends heavily on the specific needs and context of your organization and projects.

• Monorepos often work well for organizations with many interconnected projects, a strong emphasis on code sharing, and the resources to invest in robust tooling and infrastructure. Companies like Google, Facebook, and Twitter are well-known users of monorepos.
• Multirepos might be a better fit for organizations with highly independent teams and projects, a need for strict isolation, or when working with a diverse range of technologies with limited overlap.