Docs as Code treats all documentation as a codebase. Using some sort of version control like Git to manage the actual documents. It prescribes writing in a plaintext markup language like Markdown, pushing that documentation through an automated pipeline that tests the quality of the writing.
We cannot avoid mistakes. But with the right tools, we can make sure they don’t hurt too much. Git offers many ways to undo, revert, recover and fix. We’ll look at the bad things that can happen to you – and how Git can save your neck. Tobias Günther will show you how.
The move from Mercurial to Git and GitHub is imminent. With Java 16, the remaining projects – including the JDK itself – will finally move. Mercurial has been under criticism for some time now and Project Skara has presented clear results, the two corresponding JEPs have now been earmarked for Java 16. Let’s take a closer look.
Every Monday, we take a step back and look at all the cool stuff that went down during the previous week. Last week, we dove into a report that compares the speeds of Micronaut, Quarkus, and Spring Boot on JDK 14, celebrated Git’s 15th birthday with an expert check, and spoke to Vaughn Vernon, the author of the book “Implementing Domain-Driven Design.”
The version control system Git has become the de facto standard when it comes to decentralized management of source code. Hardly any other system has had such a strong influence on the way we develop software today over the past decades. For the occasion of Git’s 15th birthday, we spoke to seven experts about their experiences and wishes for the future. In our Git expert check, they also talk about what is still missing in Git and what features they like best.
The version control system Git has received its latest update. Git 2.26 sets v2 of the network fetch protocol as default and continues working on git sparse-checkout that was introduced in the previous version, which was released two months ago. Let’s see what has changed for this command and what else is new.
Gitea helps you set up your own self-hosted Git service with the use of lightweight Go code. The latest version, 1.11.0, includes a long list of updates, bug fixes, and improvements, including changing the markdown rendering to goldmark, and a new contrib command. Is self-hosting the right solution for you? See how Gitea compares to other Git hosting solutions.
Variety is the spice of life, and now there is another DevOps platform to choose from. OneDev is a new, all-in-one, open source Git server with a simple to use UI, customizable issue states and fields, and auto-refreshing issue boards. Browse some of its features and see how it compares to other popular tools. Who knows, maybe OneDev is the platform that you have been searching for.
Git 2.25 has been released. It is designed to improve partial cloning of repositories, a feature that is still considered experimental, with the new git sparse-checkout command. Let’s take a closer look and see what the version control system’s latest release has in store for us.
The goal of Gitea is creating simple, fast, painless self-hosted Git services. It is written in Go and was forked from Gogs, a similar open source project, in 2016. Its newest major release just arrived, with some new features and over 150 bug fixes. Why do people turn to self-hosting services? How does Gitea stack up to other providers or Git hosting solutions?
The newest version of Git arrived on November 3, 2019. What’s new in the open source project? Git 2.24 includes a number of notable features, bug fixes, and changes, including commit graphs enabled by default, and a newly adopted code of conduct. Let’s browse through the release notes and talk about some of the new features.
It’s been a little over a month since the last update, and now Git 2.23 is here with some new features, changes, and fixes. Some new experimental commands and new additions to existing commands are just a taste of what’s new in the latest version. Let’s take a closer look at what’s changed.
Project Skara’s goal in July last year was to look into the viable SCM alternatives to Mercurial. It looks like Git is to be OpenJDK’s new home, at least following JEP 357’s proposal. Let’s take a closer at look at what’s going on.
Source control management systems (SCM) are a part of the standard equipment of a software developer. Despite their daily usage, there are still many helpful techniques that are largely unknown. There are quite a lot of SCM tools [1]. This article refers to the freely available, distributed SCM tool Git that has a very high relevance due to its widespread use. And with only a few adaptations many of the here presented practises can also be applied to other solutions as well, for example, subversion.
