init

.custom_sources.yml

+gitlab-rails:
+  remote: "git@dev.gitlab.org:gitlab/gitlabhq.git"
+  alternative: "http://git.yes-soft.cn/hao.xu/gitlab-foss.git"
+  security: "https://gitlab.com/gitlab-org/security/gitlab-foss.git"
+  # When running it on your local machine, use the SSH version to make it easier to authenticate:
+  #security: "git@gitlab.com:gitlab-org/security/gitlab-foss.git"
+gitlab-rails-ee:
+  remote: "git@dev.gitlab.org:gitlab/gitlab-ee.git"
+  alternative: "https://jihulab.com/gitlab-cn/gitlab.git"
+  security: "https://gitlab.com/gitlab-org/security/gitlab.git"
+  # When running it on your local machine, use the SSH version to make it easier to authenticate:
+  #security: "git@gitlab.com:gitlab-org/security/gitlab.git"
+gitlab-shell:
+  remote: "git@dev.gitlab.org:gitlab/gitlab-shell.git"
+  alternative: "https://jihulab.com/gitlab-cn/gitlab-shell.git"
+  security: "https://gitlab.com/gitlab-org/security/gitlab-shell.git"
+gitlab-pages:
+  remote: "git@dev.gitlab.org:gitlab/gitlab-pages.git"
+  alternative: "https://jihulab.com/gitlab-cn/gitlab-pages.git"
+  security: "https://gitlab.com/gitlab-org/security/gitlab-pages.git"
+gitlab-exporter:
+  remote: "git@dev.gitlab.org:gitlab-org/gitlab-exporter.git"
+  alternative: "https://gitlab.com/gitlab-org/gitlab-exporter.git"
+gitlab-kas:
+  remote: "git@dev.gitlab.org:gitlab/cluster-integration/gitlab-agent.git"
+  alternative: "https://jihulab.com/gitlab-cn/cluster-integration/gitlab-agent.git"
+  security: "https://gitlab.com/gitlab-org/security/cluster-integration/gitlab-agent.git"
+docker-distribution-pruner:
+  remote: "git@dev.gitlab.org:gitlab/docker-distribution-pruner.git"
+  alternative: "https://gitlab.com/gitlab-org/docker-distribution-pruner.git"
+config_guess:
+  remote: "git@dev.gitlab.org:omnibus-mirror/config_guess.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/config_guess.git"
+omnibus:
+  remote: "https://dev.gitlab.org/gitlab/omnibus.git"
+  alternative: "https://gitlab.com/gitlab-org/omnibus.git"
+registry:
+  remote: "git@dev.gitlab.org:gitlab/container-registry.git"
+  alternative: "https://gitlab.com/gitlab-org/container-registry.git"
+  security: "https://gitlab.com/gitlab-org/security/container-registry.git"
+rb-readline:
+  remote: "git@dev.gitlab.org:omnibus-mirror/rb-readline.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/rb-readline.git"
+prometheus:
+  remote: "git@dev.gitlab.org:omnibus-mirror/prometheus.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/prometheus.git"
+alertmanager:
+  remote: "git@dev.gitlab.org:omnibus-mirror/alertmanager.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/alertmanager.git"
+node-exporter:
+  remote: "git@dev.gitlab.org:omnibus-mirror/node_exporter.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/node_exporter.git"
+postgres-exporter:
+  remote: "git@dev.gitlab.org:omnibus-mirror/postgres_exporter.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/postgres_exporter.git"
+redis-exporter:
+  remote: "git@dev.gitlab.org:omnibus-mirror/redis_exporter.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/redis_exporter.git"
+pgbouncer-exporter:
+  remote: "git@dev.gitlab.org:omnibus-mirror/pgbouncer_exporter.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/pgbouncer_exporter.git"
+gitaly:
+  remote: 'git@dev.gitlab.org:gitlab/gitaly'
+  alternative: 'https://jihulab.com/gitlab-cn/gitaly.git'
+  security: "https://gitlab.com/gitlab-org/security/gitaly.git"
+gitlab-elasticsearch-indexer:
+  remote: 'git@dev.gitlab.org:gitlab/gitlab-elasticsearch-indexer.git'
+  alternative: 'https://jihulab.com/gitlab-cn/gitlab-elasticsearch-indexer.git'
+  security: "https://gitlab.com/gitlab-org/security/gitlab-elasticsearch-indexer.git"
+logrotate:
+  remote: "git@dev.gitlab.org:omnibus-mirror/logrotate.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/logrotate.git"
+chef-acme:
+  remote: "git@dev.gitlab.org:omnibus-mirror/chef-acme.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/chef-acme.git"
+nginx:
+  remote: "git@dev.gitlab.org:omnibus-mirror/nginx.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/nginx.git"
+nginx-module-vts:
+  remote: "git@dev.gitlab.org:omnibus-mirror/nginx-module-vts.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/nginx-module-vts.git"
+ngx_security_headers:
+  remote: "git@dev.gitlab.org:omnibus-mirror/ngx_security_headers.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/ngx_security_headers.git"
+zlib:
+  remote: "git@dev.gitlab.org:omnibus-mirror/zlib.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/zlib.git"
+openssl:
+  remote: "git@dev.gitlab.org:omnibus-mirror/openssl.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/openssl.git"
+curl:
+  remote: "git@dev.gitlab.org:omnibus-mirror/curl.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/curl.git"
+omnibus-ctl:
+  remote: "git@dev.gitlab.org:omnibus-mirror/omnibus-ctl.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/omnibus-ctl.git"
+compat_resource:
+  remote: "git@dev.gitlab.org:omnibus-mirror/compat_resource.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/compat_resource.git"
+libicu:
+  remote: "git@dev.gitlab.org:omnibus-mirror/libicu.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/libicu.git"
+krb5:
+  remote: "git@dev.gitlab.org:omnibus-mirror/krb5.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/krb5.git"
+libpng:
+  remote: "git@dev.gitlab.org:omnibus-mirror/libpng.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/libpng.git"
+libjpeg-turbo:
+  remote: "git@dev.gitlab.org:omnibus-mirror/libjpeg-turbo.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/libjpeg-turbo.git"
+libtiff:
+  remote: "git@dev.gitlab.org:omnibus-mirror/libtiff.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/libtiff.git"
+exiftool:
+  remote: "git@dev.gitlab.org:omnibus-mirror/exiftool.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/exiftool.git"
+libevent:
+  remote: "git@dev.gitlab.org:omnibus-mirror/libevent.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/libevent.git"
+repmgr:
+  remote: "git@dev.gitlab.org:omnibus-mirror/repmgr.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/repmgr.git"
+jemalloc:
+  remote: "git@dev.gitlab.org:omnibus-mirror/jemalloc.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/jemalloc.git"
+go-crond:
+  remote: "git@dev.gitlab.org:omnibus-mirror/go-crond.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/go-crond.git"
+consul:
+  remote: "git@dev.gitlab.org:omnibus-mirror/consul.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/consul.git"
+ohai:
+  remote: "git@dev.gitlab.org:omnibus-mirror/ohai.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/ohai.git"
+redis:
+  remote: "git@dev.gitlab.org:omnibus-mirror/redis.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/redis.git"
+psycopg2:
+  remote: "git@dev.gitlab.org:omnibus-mirror/psycopg2.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/psycopg2.git"
+pcre2:
+  remote: "git@dev.gitlab.org:omnibus-mirror/pcre2.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/pcre2.git"
+libtensorflow_lite:
+  remote: "git@dev.gitlab.org:omnibus-mirror/tensorflow.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/tensorflow.git"
+spamcheck:
+  remote: "git@dev.gitlab.org:omnibus-mirror/spamcheck.git"
+  alternative: "https://gitlab.com/gitlab-org/gl-security/security-engineering/security-automation/spam/spamcheck.git"
+ncurses:
+  remote: "git@dev.gitlab.org:omnibus-mirror/ncurses.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/ncurses.git"
+pgbouncer:
+  remote: "git@dev.gitlab.org:omnibus-mirror/pgbouncer.git"
+  alternative: "https://gitlab.com/gitlab-org/build/omnibus-mirror/pgbouncer.git"

.gitattributes

+CHANGELOG.md merge=union
+*.rb.template gitlab-language=ruby

.gitignore

+*.gem
+.bundle
+vendor/bundle
+pkg/*
+.vagrant
+bin/*
+files/**/cache/
+vendor/cookbooks
+.ruby-gemset
+.rvmrc
+.rbenv-version
+build.txt
+Vagrantfile
+.idea
+.vscode
+*.log
+docker/RELEASE
+*.swp
+tags
+*.tags
+gitlab-licenses/*
+public/*
+config/projects/simple.rb
+.markdownlintrc
+.DS_Store
+.yardoc
+yard
+
+# These are created during a package build. We do not want to commit them
+.yarn-cache
+assets_cache
+
+build_facts
+node_modules
+
+spec/examples.txt
+
+.projections.json
+
+coverage/
+
+junit_rspec.xml
+
+support/packer/manifests

.gitlab-ci.yml

+stages:
+  - check
+  - prepare
+  - tests
+  - post-test
+  - update-cache
+  - package
+  - image
+  - scan-dependencies
+  - staging_upload
+  - package-and-image-release
+  - qa-release
+  - validate
+  - metrics
+  - aws-marketplace-release
+  - notification_fail
+  - qa
+  - verify
+
+include:
+  - local: '/gitlab-ci-config/workflow-rules.yml'
+  - local: '/gitlab-ci-config/dev-gitlab-org.yml'
+  - local: '/gitlab-ci-config/gitlab-com.yml'
+    rules:
+      - if: '$CI_SERVER_HOST == "gitlab.com"'
+
+default:
+  tags:
+    - gitlab-org
+
+variables:
+  # BUILDER_IMAGE_REGISTRY is set to
+  # `dev.gitlab.org:5005/cookbooks/gitlab-omnibus-builder` in the project
+  # settings of omnibus-gitlab mirror in dev.gitlab.org so that builds there
+  # will use images from that registry and not depend on GitLab.com
+  BUILDER_IMAGE_REGISTRY: "registry.gitlab.com/gitlab-org/gitlab-omnibus-builder"
+  # To be used for images that exist only on dev.gitlab.org
+  DEV_BUILDER_IMAGE_REGISTRY: 'dev.gitlab.org:5005/cookbooks/gitlab-omnibus-builder'
+  PUBLIC_BUILDER_IMAGE_REGISTRY: "registry.gitlab.com/gitlab-org/gitlab-omnibus-builder"
+  BUILDER_IMAGE_REVISION: "5.16.0"
+  # The registry to pull the assets image from
+  ASSET_REGISTRY: "${CI_REGISTRY}"
+  ASSET_SYNC_EXISTING_REMOTE_FILES: "keep"
+  ASSET_SYNC_GZIP_COMPRESSION: "true"
+  ASSET_PATH: "assets-${CI_COMMIT_REF_SLUG}"
+  COMPILE_ASSETS: "false"
+  RUBY_IMAGE: "ruby:3.0"
+  BUNDLE_PATH__SYSTEM: "false"
+  # Format of the auto-deploy tag for auto-deploy builds.
+  # https://gitlab.com/gitlab-org/release/docs/blob/master/general/deploy/auto-deploy.md#auto-deploy-tagging
+  AUTO_DEPLOY_TAG_REGEX: '^\d+\.\d+\.\d+\+[^ ]{7,}\.[^ ]{7,}$'
+  # Default environment for auto-deploy
+  AUTO_DEPLOY_ENVIRONMENT: 'pre'
+  OMNIBUS_GITLAB_MIRROR_ID: "14588374"
+  DOCS_GITLAB_REPO_SUFFIX: "omnibus"
+  CACHE_KEY_SUFFIX: '-v3'
+  CACHE_EDITION: "CE"
+  CACHE_POLICY: 'pull-push'
+  ISSUE_BOT_LABELS_EXTRA: "group::distribution"
+  BUNDLER_VERSION: "2.5.9"
+  GET_GEO_TAG: "0.7.4"
+  CANONICAL_PROJECT_PATH: 'gitlab-org/omnibus-gitlab'
+  SECURITY_PROJECT_PATH: 'gitlab-org/security/omnibus-gitlab'
+  DEV_PROJECT_PATH: 'gitlab/omnibus-gitlab'
+  QA_PROJECT_PATH: 'gitlab-org/build/omnibus-gitlab-mirror'
+  ARM64_RUNNER_TAG: 'arm64'
+  PACKAGE_PROMOTION_RUNNER_TAG: 'promotion'
+  NIGHTLY_REPO: 'nightly-builds'
+  NIGHTLY_FIPS_REPO: 'nightly-fips-builds'
+  QA_TESTS_UPSTREAM_PROJECT: 'gitlab-org/gitlab'
+  QA_TESTS_REF: 'master'
+
+.distribution-amd64-tags:
+  - distribution-runner
+  - amd64
+
+.distribution-arm64-tags:
+  - distribution-runner
+  - ${ARM64_RUNNER_TAG}
+
+.distribution-armhf-tags:
+  - distribution-runner
+  - armhf
+
+### For services that need a docker daemon
+.docker_job: &docker_job
+  image: "${BUILDER_IMAGE_REGISTRY}/distribution_ci_tools:${BUILDER_IMAGE_REVISION}"
+  variables:
+    DOCKER_DRIVER: overlay2
+    DOCKER_HOST: tcp://docker:2375
+  services:
+    - name: docker:23.0.5-dind
+      alias: localhost
+  tags:
+    - gitlab-org-docker
+
+.gems-cache:
+  cache:
+    key: "gems-cache-${BUILDER_IMAGE_REVISION}${CACHE_KEY_SUFFIX}"
+    paths:
+      - gems
+    policy: pull
+
+.gems-cache-os-dependent:
+  cache:
+    key: "gems-cache-${CI_JOB_IMAGE}${CACHE_KEY_SUFFIX}"
+    paths:
+      - gems
+
+.build-package: &build-package
+  - bundle exec rake cache:populate
+  - bundle exec rake cache:restore
+  - bundle exec rake build:project
+  - bundle exec rake build:package:sync
+  - bundle exec rake cache:bundle
+  - bundle exec rake build:component_shas
+
+before_script:
+  - echo "PIPELINE_TYPE detected as ${PIPELINE_TYPE}"
+  # Exit early if building on an OS for which we don't provide the specified
+  # package edition (CE/EE). For child pipelines from
+  # TRIGGERED_(CE|EE)_PIPELINE, we don't want exit early, but try to build
+  # everything.
+  - if [[ "${CI_PIPELINE_SOURCE}" != "parent_pipeline" ]]; then
+      export CE_ONLY=(Raspberry);
+      export EE_ONLY=(SLES RAT);
+      for job in "${CE_ONLY[@]}"; do
+        if [[ "${CI_JOB_NAME}" =~ ${job} ]]; then
+          if ./support/is_gitlab_ee.sh; then
+            echo "EE build found. ${CI_JOB_NAME} is run only on CE builds";
+            exit 0 ;
+          fi;
+        fi;
+      done;
+      for job in "${EE_ONLY[@]}"; do
+        if [[ "${CI_JOB_NAME}" =~ ${job} ]]; then
+          if ! ./support/is_gitlab_ee.sh; then
+            echo "CE build found. ${CI_JOB_NAME} is run only on EE builds";
+            exit 0 ;
+          fi;
+        fi;
+      done
+    fi
+  - echo $NIGHTLY
+  - mkdir -p ~/.ssh
+  - mkdir -p ~/.aws
+  - mkdir -p cache
+  - if [ -n "$DEV_GITLAB_SSH_KEY" ]; then
+      echo "$DEV_GITLAB_SSH_KEY" > ~/.ssh/id_rsa;
+      cp support/known_hosts ~/.ssh/known_hosts;
+      chmod -R 0600 ~/.ssh/;
+    fi
+  - bash scripts/ci/prepare_bundle.sh
+  - if [ -n "$NIGHTLY" ]; then
+      export STAGING_REPO=${NIGHTLY_REPO};
+      export FIPS_STAGING_REPO=${NIGHTLY_FIPS_REPO};
+    fi
+
+fetch-assets:
+  extends: .docker_job
+  stage: prepare
+  timeout: 1 hour
+  before_script: []
+  script:
+    - export VERSION=${GITLAB_ASSETS_TAG-${GITLAB_REF_SLUG-$(ruby -I. -e 'require "lib/gitlab/version"; puts Gitlab::Version.new("gitlab-rails").print')}}
+    - support/fetch_assets "${VERSION}"
+  artifacts:
+    paths:
+      - ${ASSET_PATH}
+  rules:
+    - if: '$COMPILE_ASSETS == "true"'
+      when: never
+    # NOTE (rspeicher): Checking `$AUTO_DEPLOY_COMPILE_ASSETS` as a feature flag
+    # See https://gitlab.com/gitlab-org/omnibus-gitlab/-/issues/5805
+    - if: '$AUTO_DEPLOY_COMPILE_ASSETS && $PIPELINE_TYPE =~ /AUTO_DEPLOY_BUILD_PIPELINE$/'
+      when: never
+    # Run on all pipelines including a package build (except auto-deploy tag
+    # covered above)
+    - if: '$PIPELINE_TYPE =~ /_BUILD_PIPELINE$/'
+    - if: '$PIPELINE_TYPE =~ /TRIGGERED_(CE|EE)_PIPELINE/'
+    - if: '$PIPELINE_TYPE == "TRIGGER_CACHE_UPDATE_PIPELINE"'
+    - if: '$PIPELINE_TYPE == "DURATION_PLOTTER_PIPELINE"'
+  retry: 2
+
+generate-facts:
+  extends: .gems-cache
+  stage: prepare
+  image: "${BUILDER_IMAGE_REGISTRY}/distribution_ci_tools:${BUILDER_IMAGE_REVISION}"
+  script:
+    - mkdir -p build_facts
+    - bundle exec omnibus manifest gitlab -l nothing > build_facts/version-manifest.json
+    - bundle exec rake build:generate_facts
+  artifacts:
+    paths:
+      - build_facts
+    reports:
+      dotenv: build_facts/env_vars
+  rules:
+    - if: '$PIPELINE_TYPE =~ /_BUILD_PIPELINE$/'
+    - if: '$PIPELINE_TYPE == "TRIGGER_CACHE_UPDATE_PIPELINE"'
+    - if: '$PIPELINE_TYPE =~ /_TEST_PIPELINE$/'
+    - if: '$PIPELINE_TYPE == "GITLAB_MR_PIPELINE"'
+    - if: '$PIPELINE_TYPE =~ /TRIGGERED_(CE|EE)_PIPELINE/'
+    - if: '$PIPELINE_TYPE == "DEPS_IO_VERSION_BUMP_PIPELINE"'
+    - if: '$PIPELINE_TYPE == "DEPENDENCY_SCANNING_PIPELINE"'
+    - if: '$PIPELINE_TYPE == "FORK_MR_PIPELINE"'
+    - when: never
+  needs: []
+  retry: 2
+
+.notify:
+  before_script:
+    - apk add --no-cache curl
+  image: "alpine"
+  stage: notification_fail
+
+notify:slack-fail:scheduled-master:
+  extends:
+    - .notify
+  script:
+    - ./support/notify_slack.sh "#qa-master" "☠️ Scheduled omnibus-build against master failed! ☠️ See $CI_PIPELINE_URL (triggered from $TOP_UPSTREAM_SOURCE_JOB)"
+  rules:
+    - if: '$TOP_UPSTREAM_SOURCE_JOB == null || $TOP_UPSTREAM_SOURCE_REF != "master"'
+      when: never
+    - if: '$PIPELINE_TYPE == "TRIGGERED_EE_PIPELINE"'
+      when: on_failure
+
+issue-bot:
+  stage: notification_fail
+  image: registry.gitlab.com/gitlab-org/distribution/issue-bot:latest
+  script: /issue-bot
+  rules:
+    - if: '$CI_COMMIT_REF_NAME != $CI_DEFAULT_BRANCH'
+      when: never
+    - if: '$PIPELINE_TYPE == "PROTECTED_TEST_PIPELINE"'
+      when: on_failure

.gitlab/CODEOWNERS

+# When adding a group as a code owner, make sure to invite the group to the
+# project here: https://gitlab.com/gitlab-org/omnibus-gitlab/-/project_members
+# As described in https://docs.gitlab.com/ee/user/project/code_owners.html
+
+* @gitlab-org/maintainers/distribution-build @gitlab-org/maintainers/distribution-package-configuration @gitlab-org/delivery @gitlab-org/tw-leadership
+
+# TODO: Remove @gitlab-org/maintainers/distribution-build from being a codeowner
+# of the CODEOWNERS file once we have confirmed the rest of the process is working
+.gitlab/CODEOWNERS @gitlab-org/development-leaders @gitlab-org/tw-leadership @gitlab-org/maintainers/distribution-build
+
+## Files that are excluded from required approval
+## These rules override the * rule above, so that changes to docs and templates
+## can be merged by any user who has maintainer rights, but is not included in
+## the * rule (usually technical writers).
+/.gitlab/issue_templates/*.md
+/.gitlab/merge_request_templates/*.md
+/doc/*.md
+/doc/**/*.md
+/doc/**/*.jpg
+/doc/**/*.png
+
+## Technical writing files that do not need `*` rule approval,
+## but still require an approval from a TW team DRI for each file.
+/doc/.vale/ @marcel.amirault @eread @aqualls @gitlab-org/tw-leadership
+.markdownlint.yml @marcel.amirault @eread @aqualls @gitlab-org/tw-leadership
+/doc/.markdownlint/ @marcel.amirault @eread @aqualls @gitlab-org/tw-leadership
+
+[Distribution Build] @gitlab-org/maintainers/distribution-build
+/config/
+/docker/
+/lib/
+/scripts/
+/support/
+
+## Dependency Maintainers
+/config/software/registry.rb @gitlab-org/maintainers/distribution-build @gitlab-org/maintainers/container-registry
+
+[Distribution Cookbooks] @gitlab-org/maintainers/distribution-package-configuration
+/files/
+
+^[Container Registry] @gitlab-org/maintainers/container-registry
+/files/gitlab-cookbooks/registry/
+
+^[Legal] @gitlab-org/legal-reviewers
+/support/dependency_decisions.yml
+
+^[Documentation Directories] @axil @eread
+/doc/

.gitlab/changelog_config.yml

+---
+# Settings for generating changelogs using the GitLab API. See
+# https://docs.gitlab.com/ee/api/repositories.html#generate-changelog-data for
+# more information.
+categories:
+  added: Added
+  fixed: Fixed
+  changed: Changed
+  deprecated: Deprecated
+  removed: Removed
+  security: Security
+  performance: Performance
+  other: Other
+template: |
+  {% if categories %}
+  {% each categories %}
+  ### {{ title }} ({% if single_change %}1 change{% else %}{{ count }} changes{% end %})
+
+  {% each entries %}
+  - [{{ title }}]({{ commit.reference }})\
+  {% if author.contributor %} by {{ author.reference }}{% end %}\
+  {% if commit.trailers.MR %}\
+   ([merge request]({{ commit.trailers.MR }}))\
+  {% else %}\
+  {% if merge_request %}\
+   ([merge request]({{ merge_request.reference }}))\
+  {% end %}\
+  {% end %}
+
+  {% end %}
+
+  {% end %}
+  {% else %}
+  No changes.
+  {% end %}
+# The format for tags that Omnibus uses isn't semver compliant, so we need to
+# specify a custom format here.
+#
+# We only match EE tags in this regex. Release tools tags CE first, then EE.
+# While it doesn't really matter which of the two we match, we opted to go with
+# EE tags here so we have the same behaviour; regardless of the tagging order.
+#
+# This does not affect the commits included in the range, as no changelog
+# commits are introduced between the tag commits.
+tag_regex: '^(?P<major>\d+)\.(?P<minor>\d+)\.(?P<patch>\d+)(\+(?P<pre>rc\d+))?((\.|\+)(?P<meta>ee\.\d+))?$'

.gitlab/issue_templates/Bug.md

+<!---
+Please read this!
+
+Before you create a new issue, please make sure that you already ran
+
+`sudo gitlab-ctl reconfigure`
+
+Also make sure to search in https://gitlab.com/gitlab-org/omnibus-gitlab/issues,
+to verify the issue you're about to submit isn't a duplicate.
+--->
+
+### Summary
+
+<!-- Describe in short the bug you've encountered -->
+
+### Steps to reproduce
+
+<!-- How one can reproduce the issue - this is very important -->
+
+### What is the current *bug* behavior?
+
+<!-- What actually happens -->
+
+### What is the expected *correct* behavior?
+
+<!-- What you should see instead -->
+
+### Relevant logs
+
+<details>
+<summary> Relevant logs </summary>
+<pre>
+<!-- 
+Paste any relevant logs.
+Live log output can be found with `sudo gitlab-ctl tail`.
+Log files live in `/var/log/gitlab` by default.
+-->
+
+</pre>
+</details>
+
+### Details of package version
+
+<details>
+<summary>Provide the package version installation details</summary>
+<pre>
+<!--
+For Debian, Ubuntu based systems, paste the output of:
+`dpkg-query -l "gitlab-*"`
+
+For RHEL based systems (CentOS, RHEL, OL, Scientific, OpenSUSE, SLES), paste the output of:
+`rpm -qa | grep 'gitlab'`
+
+If you can't provide these details, see https://about.gitlab.com/getting-help/ page on where to ask your question.
+-->
+
+</pre>
+</details>
+
+### Environment details
+
+* Operating System: `REPLACE-WITH-DETAILS`
+* Installation Target, remove incorrect values:
+  * Bare Metal Machine
+  * VM: Digital Ocean, AWS, GCP, Azure, Other `REPLACE-WITH-DETAILS`
+  * Other: `REPLACE-WITH-DETAILS`
+* Installation Type, remove incorrect values:
+  * New Installation
+  * Upgrade from version `REPLACE-WITH-DETAILS`
+  * Other: `REPLACE-WITH-DETAILS`
+* Is there any other software running on the machine: `REPLACE-WITH-DETAILS`
+* Is this a single or multiple node installation?
+* Resources
+  * CPU: `REPLACE-WITH-DETAILS`
+  * Memory total: `REPLACE-WITH-DETAILS`
+
+### Configuration details
+
+<details>
+<summary> Provide the relevant sections of `/etc/gitlab/gitlab.rb` </summary>
+<pre>
+<!--
+Paste the details but omit lines starting with `#`. Relevant lines can be retrieved by
+running `grep -v -e '^#' -e '^$' /etc/gitlab/gitlab.rb`. Be certain to sanitize sensitive
+configuration such as passwords and secrets.
+-->
+
+</pre>
+</details>
+
+/label ~"type::bug"

.gitlab/issue_templates/Feature Proposal.md

+<!--
+Read me first!
+
+Before you create a new issue, please make sure to search in https://gitlab.com/gitlab-org/omnibus-gitlab/issues,
+to verify that the issue you are about to submit isn't a duplicate.
+-->
+
+### Summary
+
+<!-- Describe in short the feature you are proposing -->
+
+### Proposal
+
+<!--
+Describe the problem you are trying to solve
+
+Benefits if the feature existed.
+
+End result of the proposed feature.
+-->
+
+### References
+
+<!-- Provide references related to this proposal -->
+
+/label ~"type::feature"

.gitlab/issue_templates/Remove Deprecation Message.md

+<!--
+Read me first!
+
+Before you create a new issue, please make sure to search in https://gitlab.com/gitlab-org/omnibus-gitlab/issues,
+to verify that the issue you are about to submit isn't a duplicate.
+-->
+
+## Remove deprecation messages
+
+<!--
+List here the deprecation messages you want to remove.
+-->
+
+### Preparation when creating the Issue
+
+- [ ] List all the [Remove deprecation messages](#remove-deprecation-messages) section all the deprecations you want to remove.
+- [ ] Set the milestone of this issue to [next planned required stop](https://docs.gitlab.com/ee/update/index.html#upgrade-paths), which should be after
+  the milestone when the configuration will be removed.
+
+### Preparation when executing the Issue
+
+- [ ] Verify that the related configuration got indeed removed in a previous milestone.
+- [ ] Make sure the MR removing the deprecation message is released on a [required stop](https://docs.gitlab.com/ee/update/index.html#upgrade-paths)
+  which is later than the removal of the configuration.

.gitlab/issue_templates/Security developer workflow.md

+<!--
+# Read me first!
+
+Create this issue under https://gitlab.com/gitlab-org/security/omnibus-gitlab/
+
+Set the title to: `Description of the original issue`
+-->
+
+### Prior to starting the security release work
+
+- [ ] Read the [security process for developers] if you are not familiar with it.
+- Fill out the [Links section](#links):
+  - [ ] Next to **Issue on Omnibus GitLab**, add a link to the `gitlab-org/omnibus-gitlab` issue that describes the security vulnerability.
+
+### Development
+
+- [ ] Run `scripts/security-harness` to prevent pushing to any remote besides `security/omnibus-gitlab` and `dev.gitlab.org/gitlab/omnibus-gitlab`
+- [ ] Create a new branch prefixing it with `security-`
+- [ ] Create a MR targeting `master` on [`security/omnibus-gitlab`](https://gitlab.com/gitlab-org/security/omnibus-gitlab) and use the [Security Release merge request template]
+- [ ] Follow the same code review process: Assign to a reviewer, then to a maintainer.
+
+After your merge request has been approved according to our approval guidelines, and by a team member of the AppSec team, you're ready to prepare the backports
+
+#### Backports
+
+- [ ] Once the MR is ready to be merged, create MRs targeting the latest 3 stable branches
+   * The 3 stable branches correspond to the versions in the title of the [Security Release Tracking Issue].
+   * At this point, it might be easy to squash the commits from the MR into one
+   * Depending on when development is happening, you may need to wait for the last stable branch to be created. If the ~"security-notifications" label is applied to this issue, you will receive a ping when the branch is created.
+- [ ] Create each MR targeting the stable branch `X-Y-stable`, using the [Security Release merge request template].
+   * Every merge request will have its own set of TODOs, so make sure to complete those.
+- [ ] On the "Related merge requests" section, ensure all MRs are linked to this issue.
+   * This section should only list the merge requests created for this issue: One targeting `master` and the 3 backports.
+- [ ] If this issue requires less than `4` merge requests, add the ~"reduced backports" label.
+
+#### Assigning to a release
+
+- [ ] When this issue is ready for release (all needed backports are approved and ready to be merged), apply the ~"security-target" label for it to be evaluated and linked to the next planned security release tracking issue.
+   * The `gitlab-release-tools-bot` evaluates and links issues with the label to the next planned security release tracking issue. If the bot finds the issue is not ready to be included in the security release, it will leave a comment on the issue explaining what needs to be done. 
+   * This issue will only be included in a security release if it is successfully linked to the security release tracking issue.
+
+#### Documentation and final details
+
+- [ ] Ensure the [Links section](#links) is completed.
+- [ ] Find out the versions affected (the Git history of the files affected may help you with this) and add them to the [details section](#details)
+- [ ] Fill in any upgrade notes that users may need to take into account in the [details section](#details)
+- [ ] Add Yes/No and further details if needed to the migration and settings columns in the [details section](#details)
+- [ ] Add the nickname of the external user who found the issue (and/or HackerOne profile) to the Thanks row in the [details section](#details)
+
+### Summary
+
+#### Links
+
+| Description | Link |
+| -------- | -------- |
+| Issue on [Omnibus GitLab](https://gitlab.com/gitlab-org/omnibus-gitlab/issues) | #TODO  |
+
+#### Details
+
+| Description | Details | Further details|
+| -------- | -------- | -------- |
+| Versions affected | X.Y  | |
+| Upgrade notes | | |
+| GitLab Settings updated | Yes/No| |
+| Migration required | Yes/No | |
+| Thanks | | |
+
+[security process for developers]: https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md
+[RM list]:  https://about.gitlab.com/release-managers/
+[issue as related]: https://docs.gitlab.com/ee/user/project/issues/related_issues.html#adding-a-related-issue
+[security Release merge request template]: https://gitlab.com/gitlab-org/omnibus-gitlab/-/blob/master/.gitlab/merge_request_templates/Security%20Release.md
+[Security Release Tracking Issue]: https://gitlab.com/gitlab-org/gitlab/-/issues/?label_name%5B%5D=upcoming%20security%20release
+
+/labels ~security ~"security-notifications"

.gitlab/merge_request_templates/Component upgrade.md

+<!-- After merging changes to this template, update the `Default description template for merge requests` -->
+<!-- found under Settings - General Merge Requests -->
+## What does this MR do?
+
+<!-- Briefly describe what this MR is about. -->
+
+%{first_multiline_commit}
+
+## Related issues
+
+<!-- Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. -->
+
+## Checklist
+
+See [Definition of done](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/CONTRIBUTING.md#definition-of-done).
+
+For anything in this list which will not be completed, please provide a reason in the MR discussion.
+
+### Required
+
+- [ ] MR title and description are up to date, accurate, and descriptive.
+- [ ] MR targets the appropriate branch.
+- [ ] Component test plan copied into MR description.
+- [ ] Latest merged results pipeline is green.
+- [ ] When ready for review, MR is labeled "~workflow::ready for review" per the [Distribution MR workflow](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/merge_requests.html).
+
+#### For GitLab team members
+
+If you don't have permissions to trigger pipelines for this MR, the reviewer
+should trigger these jobs for you during the review process.
+
+- [ ] The manual `Trigger:ee-package` jobs have a green pipeline running against latest commit. To debug QA failures, refer to [Investigate QA failures](https://about.gitlab.com/handbook/engineering/quality/quality-engineering/enablement-saas-platforms-qe-team/distribution/#investigate-qa-failures).
+- [ ] If `config/software` or `config/patches` directories are changed, `build-package-on-all-os` job within the `Trigger:ee-package` downstream pipeline succeeded.
+- [ ] If you are changing anything SSL related, the `Trigger:package:fips` manual job within the `Trigger:ee-package` downstream pipeline succeeded.
+- [ ] If CI/CD configuration is changed, the branch is pushed to [`dev.gitlab.org`](https://dev.gitlab.org/gitlab/omnibus-gitlab) to confirm regular branch builds aren't broken.
+
+### Expected (please provide an explanation if not completing)
+
+- [ ] Test plan indicating conditions for success has been posted and passes.
+- [ ] Documentation created or updated.
+- [ ] Tests added.
+- [ ] Integration tests added to [GitLab QA](https://gitlab.com/gitlab-org/gitlab-qa).
+- [ ] Equivalent MR/issue for the [GitLab Chart](https://gitlab.com/gitlab-org/charts/gitlab) opened.
+- [ ] Potential values for new configuration settings validated. Formats such as integer `10`, duration `10s`, URI `scheme://user:passwd@host:port` may require quotation or other special handling when rendered in a template and written to a configuration file.
+
+## Test plan
+
+<!--
+* Create a test plan file if it does already exist. Refer to
+[Upgrading software components](../upgrading-software-component#test-plans) for
+details. Consider modifying existing an existing plan to meet new requirements.
+
+* Copy the contents of the test plan here.
+-->

.gitlab/merge_request_templates/Default.md

+<!-- After merging changes to this template, update the `Default description template for merge requests` -->
+<!-- found under Settings - General Merge Requests -->
+## What does this MR do?
+
+<!-- Briefly describe what this MR is about. -->
+
+%{first_multiline_commit}
+
+## Related issues
+
+<!-- Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. -->
+
+## Checklist
+
+See [Definition of done](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/CONTRIBUTING.md#definition-of-done).
+
+For anything in this list which will not be completed, please provide a reason in the MR discussion.
+
+### Required
+
+- [ ] MR title and description are up to date, accurate, and descriptive.
+- [ ] MR targeting the appropriate branch.
+- [ ] Latest Merge Result pipeline is green.
+- [ ] When ready for review, MR is labeled "~workflow::ready for review" per the [Distribution MR workflow](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/merge_requests.html).
+
+#### For GitLab team members
+
+If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
+
+- [ ] The manual `Trigger:ee-package` jobs have a green pipeline running against latest commit.
+  - To debug QA failures, refer to the [Investigate QA failures](https://about.gitlab.com/handbook/engineering/quality/quality-engineering/enablement-saas-platforms-qe-team/distribution/#investigate-qa-failures) section.
+- [ ] If `config/software` or `config/patches` directories are changed, make sure the `build-package-on-all-os` job within the `Trigger:ee-package` downstream pipeline succeeded.
+- [ ] If you are changing anything SSL related, then the `Trigger:package:fips` manual job within the `Trigger:ee-package` downstream pipeline must succeed.
+- [ ] If CI configuration is changed, the branch must be pushed to [`dev.gitlab.org`](https://dev.gitlab.org/gitlab/omnibus-gitlab) to confirm regular branch builds aren't broken.
+
+### Expected (please provide an explanation if not completing)
+
+- [ ] Test plan indicating conditions for success has been posted and passes.
+- [ ] Documentation created/updated.
+- [ ] Tests added.
+- [ ] Integration tests added to [GitLab QA](https://gitlab.com/gitlab-org/gitlab-qa).
+- [ ] Equivalent MR/issue for the [GitLab Chart](https://gitlab.com/gitlab-org/charts/gitlab) opened.
+- [ ] Validate potential values for new configuration settings. Formats such as integer `10`, duration `10s`, URI `scheme://user:passwd@host:port` may require quotation or other special handling when rendered in a template and written to a configuration file.

.gitlab/merge_request_templates/Deprecated Configuration.md

+<!-- Read through https://docs.gitlab.com/omnibus/development/add-remove-configuration-options.html -->
+## What does this MR do?
+
+<!-- Briefly describe what this MR is about. -->
+
+## Related issues
+
+<!-- Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. -->
+
+## Deprecation schedule
+
+<!-- Customers need time to react to deprecation, the preferred warning time is 3 release milestones before a feature is actually removed. -->
+
+| Configuration Key | Deprecation Date | Removal Date |
+|-|-|-|
+| TBD | TBD | TBD |
+
+## Checklist
+
+See [Definition of done](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/CONTRIBUTING.md#definition-of-done).
+
+For anything in this list which will not be completed, please provide a reason in the MR discussion
+
+### Required
+
+- [ ] Merge Request Title, and Description are up to date, accurate, and descriptive
+- [ ] MR targeting the appropriate branch
+- [ ] MR has a green pipeline on GitLab.com
+- [ ] Pipeline is green on the [dev.gitlab.org](https://dev.gitlab.org/gitlab/omnibus-gitlab/-/pipelines) mirror for this branch if the change is touching anything besides documentation or internal cookbooks. Please note that feature branches are not automatically mirrored to dev.gitlab.org, and should be manually pushed whenever necessary.
+- [ ] `trigger-package` has a green pipeline running against latest commit
+- [ ] When ready for review, MR is labeled "~workflow::ready for review" per the [Distribution MR workflow](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/merge_requests.html)
+
+### Expected (please provide an explanation if not completing)
+
+- [ ] Test plan indicating conditions for success has been posted and passes
+- [ ] Documentation created/updated
+- [ ] Tests updated
+- [ ] Equivalent MR/issue for the [GitLab Chart](https://gitlab.com/gitlab-org/charts/gitlab) opened
+- [ ] Notify Product for inclusion in release notes

.gitlab/merge_request_templates/Documentation update.md

+## What does this MR do?
+
+<!-- Briefly describe what this MR is about. -->
+
+## Related issues
+
+<!-- Link related issues below. -->
+
+## Author's checklist
+
+- [ ] Consider taking [the GitLab Technical Writing Fundamentals course](https://gitlab.edcast.com/pathways/ECL-02528ee2-c334-4e16-abf3-e9d8b8260de4)
+- [ ] Follow the:
+  - [Documentation process](https://docs.gitlab.com/ee/development/documentation/workflow.html).
+  - [Documentation guidelines](https://docs.gitlab.com/ee/development/documentation/).
+  - [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide/).
+- [ ] When ready for review, MR is labeled "~workflow::ready for review" per the [Distribution MR workflow](https://about.gitlab.com/handbook/engineering/development/enablement/systems/distribution/merge_requests.html)
+
+If you are only adding documentation, do not add any of the following labels:
+
+- `~"feature"`
+- `~"frontend"`
+- `~"backend"`
+- `~"bug"`
+- `~"database"`
+
+These labels cause the MR to be added to code verification QA issues.
+
+## Review checklist
+
+Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on [Documentation Guidelines](https://docs.gitlab.com/ee/development/documentation/) and the [Style Guide](https://docs.gitlab.com/ee/development/documentation/styleguide/).
+
+- [ ] If the content requires it, ensure the information is reviewed by a subject matter expert.
+- Technical writer review items:
+  - [ ] Ensure docs metadata is present and up-to-date.
+  - [ ] Ensure the appropriate [labels](https://about.gitlab.com/handbook/product/ux/technical-writing/workflow/#labels) are added to this MR.
+  - If relevant to this MR, ensure [content topic type](https://docs.gitlab.com/ee/development/documentation/structure.html) principles are in use, including:
+    - [ ] The headings should be something you'd do a Google search for. Instead of `Default behavior`, say something like `Default behavior when you close an issue`.
+    - [ ] The headings (other than the page title) should be active. Instead of `Configuring GDK`, say something like `Configure GDK`.
+    - [ ] Any task steps should be written as a numbered list.
+    - If the content still needs to be edited for topic types, you can create a follow-up issue with the ~"docs-technical-debt" label.
+- [ ] Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
+- [ ] Ensure a release milestone is set.
+
+/label ~documentation ~"devops::systems" ~"group::distribution" ~"section::core platform" ~"Distribution:Build" ~"type::maintenance" ~"maintenance::refactor"
+/assign me

.gitlab/merge_request_templates/Security Release.md

+<!--
+# README first!
+This MR should be created on https://gitlab.com/gitlab-org/security/omnibus-gitlab/
+
+See [the general developer security release guidelines](https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/developer.md).
+-->
+
+## Related issues
+
+<!-- Mention the GitLab Security issue this MR is related to -->
+
+## Developer checklist
+
+- [ ] **On "Related issues" section, write down the [Omnibus GitLab Security] issue it belongs to (i.e. `Related to <issue_id>`).**
+- [ ] MR targets `master`, or `X-Y-stable` for backports.
+- [ ] Title of this MR is the same as for all backports.
+- [ ] A [CHANGELOG entry] has been included, with `Changelog` trailer set to `security`.
+- [ ] Assign to a reviewer and maintainer, per our [Code Review process].
+- [ ] For the MR targeting `master`, ensure it's approved according to our [Approval Guidelines]
+  - [ ] Approved by an AppSec engineer.
+- [ ] Merge request _must not_ close the corresponding security issue, _unless_ it targets `master`.
+
+## Reviewer checklist
+
+- [ ] Assigned to `@gitlab-release-tools-bot` with passing CI pipelines
+
+/label ~security
+
+[Omnibus GitLab Security]: https://gitlab.com/gitlab-org/security/omnibus-gitlab
+[approval guidelines]: https://docs.gitlab.com/ee/development/code_review.html#approval-guidelines
+[Code Review process]: https://docs.gitlab.com/ee/development/code_review.html
+[quick actions]: https://docs.gitlab.com/ee/user/project/quick_actions.html#quick-actions-for-issues-merge-requests-and-epics
+[CHANGELOG entry]: https://docs.gitlab.com/ee/development/changelog.html#overview

.gitlab/merge_request_templates/Stable Branch.md

+<!--
+Merging into stable branches in canonical projects is reserved for
+GitLab patch releases https://docs.gitlab.com/ee/policy/maintenance.html#patch-releases
+
+If you're backporting a security fix, please refer to the security merge request
+template https://gitlab.com/gitlab-org/omnibus-gitlab/-/blob/master/.gitlab/merge_request_templates/Security%20Release.md
+Security backport merge requests should not be opened on the Omnibus GitLab canonical project.
+-->
+
+## What does this MR do and why?
+
+_Describe in detail what merge request is being backported and why_
+
+## MR acceptance checklist
+
+This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
+
+* [ ] This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
+* [ ] The original MR has been deployed to GitLab.com (not applicable for documentation or spec changes).
+* [ ] This MR has a [severity label] assigned (if applicable).
+
+#### Note to the merge request author and maintainer
+
+The process of backporting bug fixes into stable branches is tracked as part of an
+[internal pilot]. If you have questions about this process, please:
+
+* Refer to the [internal pilot] issue for feedback or questions.
+* Refer to the [patch release runbook for engineers and maintainers] for guidance.
+
+[severity label]: https://handbook.gitlab.com/handbook/engineering/infrastructure/engineering-productivity/issue-triage/#severity
+[internal pilot]: https://gitlab.com/gitlab-com/gl-infra/delivery/-/issues/2886
+[patch release runbook for engineers and maintainers]: https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/process_new.md
+
+/assign me

.gitlab/route-map.yml

+# Documentation
+- source: /doc/(.+?)\.md/  # doc/administration/build_artifacts.md
+  public: '\1.html'  # doc/administration/build_artifacts.html

.markdownlint-cli2.yaml

+---
+# Base Markdownlint configuration
+# Extended Markdownlint configuration in doc/.markdownlint/
+# See https://github.com/DavidAnson/markdownlint/blob/main/doc/Rules.md for explanations of each rule
+config:
+  # First, set the default
+  default: true
+
+  # Per-rule settings in alphabetical order
+  code-block-style:                 # MD046
+    style: "fenced"
+  emphasis-style: false             # MD049
+  first-header-h1: true             # MD002
+  first-line-h1: false              # MD041
+  header-style:                     # MD003
+    style: "atx"
+  hr-style:                         # MD035
+    style: "---"
+  line-length: false                # MD013
+  no-duplicate-heading:             # MD024
+    siblings_only: true
+  no-emphasis-as-heading: false     # MD036
+  no-inline-html: false             # MD033
+  no-trailing-punctuation:          # MD026
+    punctuation: ".,;:!。，；：！？"
+  no-trailing-spaces: false         # MD009
+  ol-prefix:                        # MD029
+    style: "one"
+  reference-links-images: false     # MD052
+  ul-style:                         # MD004
+    style: "dash"
+
+  # Keep this item last due to length
+  proper-names:                     # MD044
+    code_blocks: false
+    html_elements: false
+    names: [
+      "Akismet",
+      "Alertmanager",
+      "AlmaLinux",
+      "API",
+      "Asana",
+      "Auth0",
+      "Azure",
+      "Bamboo",
+      "Bitbucket",
+      "Bugzilla",
+      "CAS",
+      "CentOS",
+      "Consul",
+      "Debian",
+      "DevOps",
+      "Docker",
+      "DockerSlim",
+      "Elasticsearch",
+      "Facebook",
+      "fastlane",
+      "fluent-plugin-redis-slowlog",
+      "GDK",
+      "Geo",
+      "Git LFS",
+      "git-annex",
+      "git-credential-oauth",
+      "git-sizer",
+      "Git",
+      "Gitaly",
+      "GitHub",
+      "gitlab.vim",
+      "GitLab Geo",
+      "GitLab Monitor",
+      "GitLab Operator",
+      "GitLab Pages",
+      "GitLab Rails",
+      "GitLab Runner",
+      "GitLab Shell",
+      "GitLab Workhorse",
+      "GitLab",
+      "Gitleaks",
+      "Gmail",
+      "Google",
+      "Grafana",
+      "Gzip",
+      "Helm",
+      "HipChat",
+      "ID",
+      "IP",
+      "Ingress",
+      "jasmine-jquery",
+      "JavaScript",
+      "Jaeger",
+      "Jenkins",
+      "Jira",
+      "Jira Cloud",
+      "Jira Server",
+      "jQuery",
+      "JSON",
+      "JupyterHub",
+      "Karma",
+      "Kerberos",
+      "Knative",
+      "Kubernetes",
+      "LDAP",
+      "Let's Encrypt",
+      "Markdown",
+      "markdownlint",
+      "Mattermost",
+      "Microsoft",
+      "minikube",
+      "MinIO",
+      "ModSecurity",
+      "Neovim",
+      "NGINX Ingress",
+      "NGINX",
+      "OAuth",
+      "OAuth 2",
+      "OmniAuth",
+      "OpenID",
+      "OpenShift",
+      "PgBouncer",
+      "Postfix",
+      "PostgreSQL",
+      "PowerShell",
+      "Praefect",
+      "Prometheus",
+      "Puma",
+      "puma-worker-killer",
+      "Python",
+      "Rake",
+      "Redis",
+      "Redmine",
+      "reCAPTCHA",
+      "Ruby",
+      "runit",
+      "Salesforce",
+      "SAML",
+      "Sendmail",
+      "Sentry",
+      "Service Desk",
+      "Sidekiq",
+      "Shibboleth",
+      "Slack",
+      "SMTP",
+      "SpotBugs",
+      "SSH",
+      "Tiller",
+      "TOML",
+      "Trello",
+      "Trello Power-Ups",
+      "TypeScript",
+      "Twitter",
+      "Ubuntu",
+      "Ultra Auth",
+      "Unicorn",
+      "unicorn-worker-killer",
+      "URL",
+      "WebdriverIO",
+      "YAML",
+      "YouTrack"
+    ]

.projections.json.example

+{
+  "lib/*.rb": {
+    "alternate": "spec/lib/{}_spec.rb",
+    "type": "source"
+  },
+  "spec/lib/*_spec.rb": {
+    "alternate": "lib/{}.rb",
+    "type": "test",
+    "dispatch": "bundle exec rspec {file}"
+  },
+  "files/gitlab-cookbooks/*.rb" : {
+    "alternate": "spec/chef/cookbooks/{}_spec.rb",
+    "type": "source"
+  },
+  "spec/chef/cookbooks/*_spec.rb": {
+    "alternate": "files/gitlab-cookbooks/{}.rb",
+    "type": "test"
+  },
+  "files/gitlab-ctl-commands/*.rb" : {
+    "alternate": "spec/chef/gitlab-ctl-commands/{}_spec.rb",
+    "type": "source"
+  },
+  "spec/chef/gitlab-ctl-commands/*_spec.rb": {
+    "alternate": "files/gitlab-ctl-commands/{}.rb",
+    "type": "test"
+  },
+  "files/gitlab-ctl-commands-ee/*.rb" : {
+    "alternate": "spec/chef/gitlab-ctl-commands-ee/{}_spec.rb",
+    "type": "source"
+  },
+  "spec/chef/gitlab-ctl-commands-ee/*_spec.rb": {
+    "alternate": "files/gitlab-ctl-commands-ee/{}.rb",
+    "type": "test"
+  }
+}

.rspec

+--color --format RspecJunitFormatter --out junit_rspec.xml --format documentation