Yet another tool for updating dependencies

Updating dependencies in Go projects can be a tedious and time-consuming process, especially when dealing with multiple repositories. In this article, the author shares the experience of developing the go-mod-bump script, which significantly simplifies this task by automating routine operations and minimizing the risk of errors. [Read More]

Let's Encrypt on Ubuntu 24.04 LTS: A step-by-step guide to obtaining and managing SSL certificates using Certbot

This guide provides comprehensive instructions for acquiring and managing Let’s Encrypt certificates on an Ubuntu 24.04 LTS server utilizing the Certbot tool. It covers both concise commands for quick certificate acquisition and an in-depth explanation of the process, including troubleshooting potential issues. [Read More]

Best practices — code self-review in a review application

Regular self-review of code in merge requests is not just a good habit but a tool that enhances code quality and team efficiency by enabling early detection and correction of errors.

I regularly review my newly written code within the same application/tool (specifically GitLab) where I review my colleagues’ code. This helps me see my code as if in a mirror, allowing me to spot more flaws before submitting the code for review. I’ve developed this habit a long time ago, but I’ve recently revisited it and decided to write about it.

[Read More]

Check actuality of go.mod and go.sum

It happens in practice that you have to revise a merge request and see suspicious changes in go.mod and go.sum, maybe only one file is changed, and a legitimate question arises, whether these changes are necessary, or whether it was accidentally added to a commit, maybe a colleague forgot to add another file to the commit or to run go mod tidy after removing a dependency? Or maybe it was you yourself who added extra changes in previous commits?

[Read More]
golang  go  gitlab  ci 

The substitution of the address of the remote repository

In git, you can replace some part of the remote repository address (part of the remote addresses) in all repositories using the global config and also this will be given when setting up a specific repository.

We simplify the move from Github <–> Gitlab <–> Bitbucket

If for example you moved from Github to Gitlab and you have locally many projects in which you need to update remote then you can do it globally until you replace remote in all repositories or again No need to use Github.

[Read More]

Submitting changes to several git repositories

Detailed setting description

Let’s start with the usual settings remote

git remote add origin https://github.com/xorcare/example.git

Further, what would happen automatically push in the additional repository, you need to run the following command

git remote set-url --add --push origin https://bitbucket.org/xorcare/example.git

After executing this command, we get the situation that fetch changes occur from Github, but sending the changes push to the repository ** Bitbucket **, in order to return sending the changes to the repository Github and get The desired result with sending changes to both repositories needs to execute one more command.

[Read More]

My first post

This is my first post created with hugo!