dri 0.11.0 → 1.1.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 030e595feea9f3659c75e7079815b88eb654b124a338211f9226cb979ad73a5c
-  data.tar.gz: 29ff03db73c44f4aee4d905820e423477e43a182cbc85677ff21a0ea54c98a28
+  metadata.gz: 5645bd9d3338211c2358afd90fdc3ad69c1ba60f517024978601fa7c8f2893e1
+  data.tar.gz: b047d324d60bb9e23e39b66e3fad29c7e27be5867c463d8a15abdc901251e161
 SHA512:
-  metadata.gz: cf0b085cff259d0e0bb3f3cffe31699bb50c6b900239d1cad1cd270333097094ae73d0478fe870681d8609f968bbea8a26c85c900c8717c65447e3c5266672cc
-  data.tar.gz: 0da07b06c6052457549eac9b7f116248dd4d534dee659a3fa8bcccb4d55fd796fd4ae4d328914d6ed1e4cf7026fe1fab9cfda2f9bced61d0848eb4276c49ba08
+  metadata.gz: bf9d19efe7b0a7ad7afa547d89a330adc31bde0a3f7dfc1c95fe23929aef56bd173bf7ee942a5afcf3e63593ae8d87a968a0c9b1f62d58750adfa7d8a5a24597
+  data.tar.gz: c1a9095caf1824f2865e49deeaaef8293e86925edb3e92c47518f5355fa87efe97ee9364eea98cd1096d548290db5a417d0bdc044b10cb0f0d799cdb22d2073e

data/.gitlab/changelog_config.yml

@@ -0,0 +1,13 @@
+---
+# 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

data/.gitlab/merge_request_templates/Default.md

@@ -0,0 +1,27 @@
+## What does this MR do and why?
+
+_Describe in detail what your merge request does and why._
+
+<!--
+Please keep this description updated with any discussion that takes place so
+that reviewers can understand your intent. Keeping the description updated is
+especially important if they didn't participate in the discussion.
+-->
+
+## Screenshots or screen recordings
+
+_These are strongly recommended to assist reviewers and reduce the time to merge your change._
+
+## How to set up and validate locally
+
+_Numbered steps to set up and validate the change are strongly suggested._
+
+## MR acceptance checklist
+
+This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
+
+* [ ] I have evaluated the [MR acceptance checklist](https://docs.gitlab.com/ee/development/code_review.html#acceptance-checklist) for this MR.
+
+/label ~"type::maintenance" ~Quality
+
+<!-- template sourced from https://gitlab.com/gitlab-org/ruby/gems/dri/-/blob/master/.gitlab/merge_request_templates/Default.md -->

data/.gitlab/merge_request_templates/Release.md

@@ -1,28 +1,13 @@
+<!-- Replace `<PREVIOUS_VERSION>` with the previous version number here, `<COMMIT_UPDATING_VERSION>` with the latest
+commit from this merge request, and `<NEW_VERSION>` with the upcoming version number. -->
 ## Diff
-<!-- Replace `v0.9.0` with the previous DRI release, and `55ddcace1c166fa2323d4e556262eba6b274230a` with the latest commit from https://gitlab.com/gitlab-org/quality/dri/-/commits/master that will be included in the release -->
-https://gitlab.com/gitlab-org/quality/dri/-/compare/v0.9.0...55ddcace1c166fa2323d4e556262eba6b274230a
 
-## Release Notes
+https://gitlab.com/gitlab-org/ruby/gems/dri/-/compare/<PREVIOUS_VERSION>...<COMMIT_UPDATING_VERSION>
 
-```markdown
-### Features
-- !aaa <Title of the aaa MR>
+## Checklist
 
-### Bug Fixes
-- !bbb <Title of the bbb MR>
+- [ ] Diff link is up-to-date.
+- [ ] Check the release notes: https://gitlab.com/api/v4/projects/gitlab-org/ruby/gems/dri/repository/changelog?version=<NEW_VERSION>
+- [ ] Based on the diff and the release notes, `version.rb` is updated, according to [SemVer](https://semver.org).
 
-### Maintenance
-- !ccc <Title of the ccc MR>
-```
-
-## Checklists 
-
-### Before merging:
-  - [ ] MR title is set to `Bump version to <version>`, where `<version>` is the new version, according to [SemVer](https://semver.org/).
-  - [ ] Diff link is up-to-date.
-  - [ ] Release notes are accurate.
-  - [ ] `lib/dri/version.rb` is updated with the new version number.
-  - [ ] `bundle update` was run to update `Gemfile.lock` with the new version number.
-
-### After merging:
-  - [ ] Update the release notes for the [newly created tag](https://gitlab.com/gitlab-org/quality/dri/-/tags) with the release notes from this MR.
+/label ~"type::maintenance" ~"dx::pipeline"

data/.gitlab-ci.yml

@@ -1,5 +1,5 @@
 .job_base:
-  image: registry.gitlab.com/gitlab-org/gitlab-build-images/debian-bullseye-ruby-${RUBY_VERSION}:bundler-2.3
+  image: registry.gitlab.com/gitlab-org/gitlab-build-images/${BUILD_OS}-${OS_VERSION}-ruby-${RUBY_VERSION}
   variables:
     BUNDLE_PATH: vendor/bundle
     BUNDLE_SUPPRESS_INSTALL_USING_MESSAGES: "true"
@@ -19,14 +19,16 @@
     - if: '$CI_PIPELINE_SOURCE == "merge_request_event"'
 
 include:
+  - component: gitlab.com/gitlab-org/components/gem-release/gem-release@~latest
   - project: gitlab-org/quality/pipeline-common
     ref: 1.2.3
     file:
-      - /ci/gem-release.yml
       - /ci/ref-update.gitlab-ci.yml
 
 variables:
-  RUBY_VERSION: "3.1"
+  BUILD_OS: "debian"
+  OS_VERSION: "bookworm"
+  RUBY_VERSION: "3.1.5"
 
 stages:
   - build
@@ -53,6 +55,6 @@ rspec:
   extends: .job_base
   parallel:
     matrix:
-      - RUBY_VERSION: ['3.0', '3.1']
+      - RUBY_VERSION: ['3.1.5', '3.2.4']
   script:
     - bundle exec rspec --force-color

data/.ruby-version

@@ -1 +1 @@
-3.1.4
+3.2.4

data/.tool-versions

@@ -1 +1 @@
-ruby 3.1.4
+ruby 3.2.4

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at remy@rymai.me. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

data/Gemfile.lock

@@ -1,7 +1,8 @@
 PATH
   remote: .
   specs:
-    dri (0.11.0)
+    dri (1.1.0)
+      activesupport (~> 7.1)
       amatch (~> 0.4.1)
       gitlab (~> 4.19)
       httparty (~> 0.21.0)
@@ -20,14 +21,20 @@ PATH
       tty-prompt (~> 0.23.1)
       tty-spinner (~> 0.9)
       tty-table (~> 0.12.0)
+      zeitwerk (~> 2.6)
 
 GEM
   remote: https://rubygems.org/
   specs:
-    activesupport (7.0.6)
+    activesupport (7.1.2)
+      base64
+      bigdecimal
       concurrent-ruby (~> 1.0, >= 1.0.2)
+      connection_pool (>= 2.2.5)
+      drb
       i18n (>= 1.6, < 2)
       minitest (>= 5.1)
+      mutex_m
       tzinfo (~> 2.0)
     addressable (2.8.4)
       public_suffix (>= 2.0.2, < 6.0)
@@ -35,11 +42,16 @@ GEM
       mize
       tins (~> 1.0)
     ast (2.4.2)
+    base64 (0.2.0)
+    bigdecimal (3.1.5)
     coderay (1.1.3)
     concurrent-ruby (1.2.2)
+    connection_pool (2.4.1)
     crack (0.4.5)
       rexml
     diff-lcs (1.5.0)
+    drb (2.2.0)
+      ruby2_keywords
     gitlab (4.19.0)
       httparty (~> 0.20)
       terminal-table (>= 1.5.1)
@@ -61,6 +73,7 @@ GEM
       rexml
     launchy (2.5.2)
       addressable (~> 2.8)
+    lefthook (1.11.8)
     markdown-tables (1.1.1)
     method_source (1.0.0)
     mini_mime (1.1.2)
@@ -68,6 +81,7 @@ GEM
     mize (0.4.1)
       protocol (~> 2.0)
     multi_xml (0.6.0)
+    mutex_m (0.2.0)
     parallel (1.23.0)
     parser (3.2.2.3)
       ast (~> 2.4.1)
@@ -130,6 +144,7 @@ GEM
       rubocop-capybara (~> 2.17)
       rubocop-factory_bot (~> 2.22)
     ruby-progressbar (1.13.0)
+    ruby2_keywords (0.0.5)
     ruby_parser (3.20.1)
       sexp_processor (~> 4.16)
     sexp_processor (4.17.0)
@@ -182,11 +197,13 @@ GEM
       concurrent-ruby (~> 1.0)
     unicode-display_width (2.4.2)
     unicode_utils (1.4.0)
+    vcr (6.2.0)
     webmock (3.18.1)
       addressable (>= 2.8.0)
       crack (>= 0.3.2)
       hashdiff (>= 0.4.0, < 2.0.0)
     wisper (2.0.1)
+    zeitwerk (2.6.13)
 
 PLATFORMS
   ruby
@@ -194,10 +211,12 @@ PLATFORMS
 DEPENDENCIES
   dri!
   gitlab-styles (~> 10)
+  lefthook (~> 1.3)
   pry (~> 0.14.1)
   rake (~> 13.0)
   rspec (~> 3.10.0)
   timecop (~> 0.9.1)
+  vcr (~> 6.2.0)
   webmock (~> 3.5)
 
 BUNDLED WITH

data/README.md

@@ -1,93 +1,88 @@
-# DRI
+# DRI Gem
 
-So, are you the **D**irectly **R**esponsible **I**ndividual for GitLab's QA pipelines this week? Looking for a gem to help triage and report failing tests? Look no further.
-
-Welcome to your new gem! DRI is a CLI ready to help:
+The DRI (Directly Responsible Individual) gem is your CLI companion for managing GitLab's QA pipelines. Tailored for those in charge of pipeline quality assurance, it simplifies the triage and reporting of failing tests. Key features include:
 
 - Fetching failing test cases by pipeline
-- Reporting at the end of the timezone shift
-- View today's newest and untriaged failures
-- Mark actions on failures
+- Reporting failures at the end of the timezone shift
+- Viewing today's newest and untriaged failures
+- Marking actions on failures
 
-... and more
 
 ## Installation
 
-To install the `dri` gem:
+Install dri using the following command:
 
 ```shell
 $ gem install dri
 ```
 
-And then execute `dri` to see all available options:
+Execute `dri` to see all available options:
 
 ```shell
 $ dri
 ```
 
-## Usage
+## Installing from source
 
-### Configuration
+After cloning this repository, build dri from source using the following command:
 
-To use `dri` fully it is necessary to have:
+```shell
+$ gem build dri.gemspec
+```
 
-- a Personal Access Token
-- a triage emoji
+A gemfile will be generated with the current version number, e.g. `dri-0.11.0.gem`. Install using the command:
 
-The emoji is the [Award/My Reaction](https://docs.gitlab.com/ee/user/award_emojis.html) emoji associated with the failure issues to group all failures triaged on a given day. This emoji is a personal choice. Note that the same emoji should be used only while triaging failures and not associated with other issues out of the scope of triage.
+```shell
+$ gem install dri-0.11.0.gem
+```
 
-To set up your personal profile:
+## Getting Started
+
+### Configuration
+
+Before diving into dri, ensure you have:
+
+* A Personal Access Token for authentication.
+* A triage emoji to mark triaged failures
+
+Configure your profile with:
 
 ```shell
 $ dri init
 ```
 
-To verify the profile is correctly set:
+To view or edit your profile:
 
 ```shell
 $ dri profile
 ```
 
-### Commands
-
-- [1. init](#1-init)
-- [2. profile](#2-profile)
-- [3. fetch](#3-fetch)
-  - failures
-  - testcases
-  - triaged
-  - featureflags
-  - runbooks
-- [4. publish](#4-publish)
-  - report
-- [5. rm](#5-rm)
-  - emoji
-  - profile
-  - reports
-- [6. incidents](#6-incidents)
-- [7. analyze](#7-analyze)
-  - stacktraces
-- [8. version](#8-version)
-- [9. faq](#8-faq)
-
-#### 1. init
+### Usage
 
 ```shell
-$ dri init
+$ dri help
 ```
 
-Initializes the `dri` CLI with necessary configurations to run smoothly.
+`dri` supports a variety of commands to streamline your workflow:
 
-#### 2. profile
+- init: Set up dri with necessary configurations.
+- profile: Display or edit your user profile.
+- fetch: Retrieve information on failures, test cases, triaged issues, feature flags, and more.
+- publish: Generate and publish reports.
+- rm: Remove emojis, profiles, or reports.
+- incidents: View active or mitigated incidents.
+- analyze: Analyze stack traces for common failures.
+- version: Check the installed version of dri.
+- faq: Access FAQs related to on-call operations.
 
-```shell
-$ dri profile
-```
 
-Shows the current profile associated after initial configuration.
-Pass the option `--edit` to edit the current profile.
+#### Command Details
 
-#### 3. fetch
+- fetch: Use options like --start_date, --end_date, and --cutoff to customize your queries.
+- publish report: Customize reports with --format, --dry-run, --actions, and --feature-flags options.
+- rm: Manage your environment by cleaning up emojis, profiles, or locally stored reports.
+
+Example Commands:
 
 ```shell
 $ dri fetch failures
@@ -96,13 +91,8 @@ $ dri fetch failures
 Fetches today's opened failures and lists them according to their triage status.
 Helpful to understand if there are missing recent failures to be reviewed.
 
-There is the possibility to customise the timeframe for such failures by passing a
-`--start_date=DD-MM-YYYY` and `--end_date=DD-MM-YYYY`. It is also possible to pass
-a `--cutoff=HH:MM` to just show failures after a certain period of the day. The cutoff
-time will be converted to UTC.
-
-Smoke and Reliable failures will be highlighted in bold and in between *'s. These require
-to have set `QA_INFLUXDB_URL` and `QA_INFLUXDB_TOKEN` environment variables to be found in 1Password.
+**Note:**  Smoke and Reliable failures will be highlighted in bold and in between *'s. These require
+to have set `QA_INFLUXDB_URL` and `QA_INFLUXDB_TOKEN` environment variables, to be found in 1Password.
 
 ```shell
 $ dri fetch testcases
@@ -116,20 +106,13 @@ To filter the pipelines, pass the `--filter-pipelines` options to multi-select t
 $ dri fetch triaged
 ```
 
-Fetches triaged failures which use the triage emoji specified in `dri profile`.
-
-```shell
-$ dri fetch featureflags
-```
-
-Fetches a list of today's feature flag changes, including the date and time in UTC of when the change occurred as well as a link to the corresponding issue from the feature-flag-log project.
+Fetches triaged failures.
 
 ```shell
 $ dri fetch pipelines
 ```
 
 Fetches a table containing last executed pipeline and its test report link for all monitored pipelines.
-The timestamps are in UTC
 
 ```shell
 $ dri fetch runbooks [runbook]
@@ -138,14 +121,11 @@ $ dri fetch runbooks [runbook]
 Fetches a runbook from the [runbooks](https://gitlab.com/gitlab-org/quality/runbooks) project.
 If `[runbook]` is omitted, the command will prompt the user to select from a list of available runbooks.
 
-#### 4. publish
-
 ```shell
 $ dri publish report
 ```
 
-Publishes a handover report on the latest triage issue, in the [pipeline-triage](https://gitlab.com/gitlab-org/quality/pipeline-triage) project.
-The report includes automatically both triaged failures and incidents.
+Publishes a handover report on the latest weekly triage issue.
 
 **Options**
 
@@ -157,22 +137,13 @@ $ dri publish report --actions # activate the actions prompt for each failure
 $ dri publish report --feature-flags # includes a summary of the feature flag changes on each environment
 $ dri publish report --update # update the report note if has already been posted
 ```
-
+---
 **Note:** These options above can be combined like:
 
 ```shell
 $ dri publish report --format=list --dry-run --actions --update
 ```
-
-**Actions**
-
-When using `--actions` a set of actions are prompt on each failure. Use `Space` to
-mark several actions: `pinged SET`, `quarantined`, `reproduced`, `transient`.
-Hitting `Enter` without a selected action will skip marking the actions for a given
-failure.
-
-#### 5. rm
-
+---
 ```shell
 $ dri rm emoji
 ```
@@ -193,41 +164,60 @@ $ dri rm profile
 
 Removes the profile currently in use.
 
-#### 6. incidents
-
 ```shell
 $ dri incidents
 ```
 
 Have a quick look at currently active/mitigated incidents on GitLab services.
 
-#### 7. analyze
-
 ```shell
-$ dri analyze stacktraces
+$ dri faq
 ```
-Searches through any open test failure issues and publishes a report that identifies
-issues that have similar stack traces. 
-This may be useful to identify situations where a common test failure is presenting 
-itself across multiple individual test cases, over a period of time. 
 
-#### 8. version
+Returns a list of questions and answers related to on-call operations. This leverages
+existing pages of documentation, redirecting directly to the relevant section to help
+with a problem.
+
+## Development
+
+### Initial setup
+- Check out the repo [dri](https://gitlab.com/gitlab-org/ruby/gems/dri)
+- Then run 
 
 ```shell
-$ dri version
+bundle install
 ```
 
-`dri` gem version.
-
-#### 9. faq
+### Activate lefthook locally
 
 ```shell
-$ dri faq
+lefthook install
 ```
 
-Returns a list of questions and answers related to on-call operations. This leverages
-existing pages of documentation, redirecting directly to the relevant section to help
-with a problem.
+## Release
+
+[Automated gem release process](https://gitlab.com/gitlab-org/components/gem-release/-/tree/main?ref_type=heads#gem-release-component) is used to release new version of `dri` through pipelines, and this will:
+
+- Publish the gem: https://rubygems.org/gems/dri
+- Add a release in the `dri` project: https://gitlab.com/gitlab-org/ruby/gems/dri/-/releases
+- Populate the release log with the API contents. For example: https://gitlab.com/api/v4/projects/52612795/repository/changelog?version=1.0.0
+
+### Before release
+
+Make sure to include a changelog entry in your commit message and read the [changelog entries section](https://docs.gitlab.com/ee/development/changelog.html).
+
+If you forget to set the changelog entry in your commit messages, you can also edit the release notes after it's being released.
+
+### Steps to release
+
+- Update the version number in `lib/dri/version.rb` with the new gem version.
+- Run `bundle install` locally to update gem version in `Gemfile.lock` .
+- Use the `Release` merge request template and create a merge request to submit these changes. Then get the merge request merged by a maintainer.
+
+This will then be packaged into a gem and pushed to [rubygems.org](https://rubygems.org) by the CI/CD.
+
+For example: [Upgrades gem from 2.7.0 to 2.8.0](https://gitlab.com/gitlab-org/ruby/gems/gitlab_quality-test_tooling/-/merge_requests/286).
+
 ## Copyright
 
 Copyright (c) 2022 GitLab, Inc. See [MIT License](LICENSE.txt) for further details.

data/dri.gemspec

@@ -22,6 +22,7 @@ Gem::Specification.new do |spec|
   spec.executables   = spec.files.grep(%r{^exe/}) { |f| File.basename(f) }
   spec.require_paths = ['lib']
 
+  spec.add_dependency 'activesupport', '~> 7.1'
   spec.add_dependency 'amatch', '~> 0.4.1'
   spec.add_dependency "gitlab", "~> 4.19"
   spec.add_dependency 'httparty', '~> 0.21.0'
@@ -40,11 +41,14 @@ Gem::Specification.new do |spec|
   spec.add_dependency 'tty-prompt', '~> 0.23.1'
   spec.add_dependency 'tty-spinner', '~> 0.9'
   spec.add_dependency 'tty-table', '~> 0.12.0'
+  spec.add_dependency 'zeitwerk', '~> 2.6'
 
   spec.add_development_dependency 'gitlab-styles', '~> 10'
+  spec.add_development_dependency "lefthook", "~> 1.3"
   spec.add_development_dependency "pry", "~> 0.14.1"
   spec.add_development_dependency 'rake', "~> 13.0"
   spec.add_development_dependency 'rspec', '~> 3.10.0'
   spec.add_development_dependency "timecop", "~> 0.9.1"
+  spec.add_development_dependency 'vcr', '~> 6.2.0'
   spec.add_development_dependency 'webmock', '~> 3.5'
 end

data/exe/dri

@@ -3,7 +3,8 @@
 
 lib_path = File.expand_path('../lib', __dir__)
 $LOAD_PATH.unshift(lib_path) unless $LOAD_PATH.include?(lib_path)
-require 'dri/cli'
+
+require 'dri'
 
 Signal.trap('INT') do
   warn("\n#{caller.join("\n")}: interrupted")

data/lefthook.yml

@@ -0,0 +1,24 @@
+# Lefthook configuration. For more information, see:
+# https://lefthook.dev/configuration/index.html
+
+pre-push:
+  parallel: true
+  commands:
+    # Run ruby linting
+    rubocop:
+      run: bundle exec rubocop
+      glob: '*.rb'
+
+    # Changelog git trailer for the first commit of the branch
+    changelog-on-first-commit:
+      run: |
+        git fetch origin main
+        first_commit_message=$(git log --format=%B -n 1 $(git log origin/main..HEAD --pretty=format:"%h" | tail -1))
+        if ! echo ${first_commit_message} | grep "Changelog:"; then
+          echo Could not find a Changelog: git trailer on the first commit for this branch.
+          echo
+          echo Please add a trailer by amending the git commit message.
+          echo
+          echo See https://docs.gitlab.com/ee/development/changelog.html#overview for more info.
+          exit 1
+        fi