<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>gitlab on ashikov.ru</title><link>https://ashikov.ru/en/tags/gitlab/</link><description>Recent content in gitlab on ashikov.ru</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 09 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://ashikov.ru/en/tags/gitlab/index.xml" rel="self" type="application/rss+xml"/><item><title>Where Deployment Actually Ends</title><link>https://ashikov.ru/en/notes/where-deployment-actually-ends/</link><pubDate>Wed, 09 Sep 2026 00:00:00 +0000</pubDate><guid>https://ashikov.ru/en/notes/where-deployment-actually-ends/</guid><description>Why a successful GitOps flow does not prove publication, and how checking the expected revision ties a release to the site response.</description></item><item><title>Documentation as a Contract: Keeping CI Documentation in Sync with the Pipeline</title><link>https://ashikov.ru/en/notes/documentation-as-contract-ci-pipeline/</link><pubDate>Mon, 31 Aug 2026 00:00:00 +0000</pubDate><guid>https://ashikov.ru/en/notes/documentation-as-contract-ci-pipeline/</guid><description>How to turn critical claims about CI into contract tests that make documentation drift visible when the pipeline changes.</description></item></channel></rss>