Commit 21a47586 authored by Marcel Amirault's avatar Marcel Amirault Committed by Albert Salim

Add back the CI job that makes sure deprecations doc is in sync

parent 29472ba1
...@@ -76,3 +76,16 @@ ui-docs-links lint: ...@@ -76,3 +76,16 @@ ui-docs-links lint:
needs: [] needs: []
script: script:
- bundle exec haml-lint -i DocumentationLinks - bundle exec haml-lint -i DocumentationLinks
docs-lint deprecations:
variables:
SETUP_DB: "false"
extends:
- .default-retry
- .rails-cache
- .default-before_script
- .docs:rules:deprecations
stage: lint
needs: []
script:
- bundle exec rake gitlab:docs:check_deprecations
...@@ -165,6 +165,13 @@ ...@@ -165,6 +165,13 @@
- ".markdownlint.yml" - ".markdownlint.yml"
- "scripts/lint-doc.sh" - "scripts/lint-doc.sh"
.docs-deprecations-patterns: &docs-deprecations-patterns
- "doc/deprecations/index.md"
- "data/deprecations/*.yml"
- "data/deprecations/templates/_deprecation_template.md.erb"
- "lib/tasks/gitlab/docs/compile_deprecations.rake"
- "tooling/deprecations/docs.rb"
.bundler-patterns: &bundler-patterns .bundler-patterns: &bundler-patterns
- '{Gemfile.lock,*/Gemfile.lock,*/*/Gemfile.lock}' - '{Gemfile.lock,*/Gemfile.lock,*/*/Gemfile.lock}'
...@@ -530,6 +537,11 @@ ...@@ -530,6 +537,11 @@
changes: *docs-patterns changes: *docs-patterns
when: on_success when: on_success
.docs:rules:deprecations:
rules:
- <<: *if-default-refs
changes: *docs-deprecations-patterns
################## ##################
# GraphQL rules # # GraphQL rules #
################## ##################
......
...@@ -17,15 +17,23 @@ sole discretion of GitLab Inc. ...@@ -17,15 +17,23 @@ sole discretion of GitLab Inc.
<!-- vale off --> <!-- vale off -->
<!-- <!--
DO NOT EDIT THIS PAGE DIRECTLY
This page is automatically generated from the YAML files in `/data/deprecations` by the rake task This page is automatically generated from the YAML files in `/data/deprecations` by the rake task
located at `lib/tasks/gitlab/docs/compile_deprecations.rake`. located at `lib/tasks/gitlab/docs/compile_deprecations.rake`.
Do not edit this page directly. For deprecation authors (usually Product Managers and Engineering Managers):
- To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template.
- For more information about authoring deprecations, check the the deprecation item guidance:
https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-deprecation-entry
To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template. For deprecation reviewers (Technical Writers only):
To update this doc, run `bin/rake gitlab:docs:compile_deprecations`. - To update the deprecation doc, run: `bin/rake gitlab:docs:compile_deprecations`
To verify this doc is up to date, run `bin/rake gitlab:docs:check_deprecations` - To verify the deprecations doc is up to date, run: `bin/rake gitlab:docs:check_deprecations`
- For more information about updating the deprecation doc, see the deprecation doc update guidance:
https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc
--> -->
<% if milestones.any? -%> <% if milestones.any? -%>
<%- milestones.each do |milestone| %> <%- milestones.each do |milestone| %>
......
...@@ -17,15 +17,23 @@ sole discretion of GitLab Inc. ...@@ -17,15 +17,23 @@ sole discretion of GitLab Inc.
<!-- vale off --> <!-- vale off -->
<!-- <!--
DO NOT EDIT THIS PAGE DIRECTLY
This page is automatically generated from the YAML files in `/data/deprecations` by the rake task This page is automatically generated from the YAML files in `/data/deprecations` by the rake task
located at `lib/tasks/gitlab/docs/compile_deprecations.rake`. located at `lib/tasks/gitlab/docs/compile_deprecations.rake`.
Do not edit this page directly. For deprecation authors (usually Product Managers and Engineering Managers):
- To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template.
- For more information about authoring deprecations, check the the deprecation item guidance:
https://about.gitlab.com/handbook/marketing/blog/release-posts/#creating-a-deprecation-entry
To add a deprecation, use the example.yml file in `/data/deprecations/templates` as a template. For deprecation reviewers (Technical Writers only):
To update this doc, run `bin/rake gitlab:docs:compile_deprecations`. - To update the deprecation doc, run: `bin/rake gitlab:docs:compile_deprecations`
To verify this doc is up to date, run `bin/rake gitlab:docs:check_deprecations` - To verify the deprecations doc is up to date, run: `bin/rake gitlab:docs:check_deprecations`
- For more information about updating the deprecation doc, see the deprecation doc update guidance:
https://about.gitlab.com/handbook/marketing/blog/release-posts/#update-the-deprecations-doc
--> -->
## 14.4 ## 14.4
......
...@@ -21,7 +21,7 @@ namespace :gitlab do ...@@ -21,7 +21,7 @@ namespace :gitlab do
if doc == contents if doc == contents
puts "Deprecations doc is up to date." puts "Deprecations doc is up to date."
else else
format_output('Deprecations doc is outdated! Please update it by running `bundle exec rake gitlab:docs:compile_deprecations`.') format_output('Deprecations doc is outdated! You (or your technical writer) can update it by running `bin/rake gitlab:docs:compile_deprecations`.')
abort abort
end end
end end
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment