summaryrefslogtreecommitdiff
path: root/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml
diff options
context:
space:
mode:
Diffstat (limited to 'data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml')
-rw-r--r--data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml12
1 files changed, 6 insertions, 6 deletions
diff --git a/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml b/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml
index cda67e53b8e..f738b71f1b7 100644
--- a/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml
+++ b/data/deprecations/14-8-remove-support-for-fixup-in-commit-message-triggering-draft-status.yml
@@ -1,9 +1,9 @@
-- name: "`fixup!` commit messages setting draft status of associated Merge Request" # The name of the feature to be deprecated
- announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
- announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
- removal_milestone: "15.0" # The milestone when this feature is planned to be removed
- removal_date: "2022-06-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed.
- body: | # Do not modify this line, instead modify the lines below.
+- name: "`fixup!` commit messages setting draft status of associated Merge Request" # The name of the feature to be deprecated
+ announcement_milestone: "14.8" # The milestone when this feature was first announced as deprecated.
+ announcement_date: "2022-02-22" # The date of the milestone release when this feature was first announced as deprecated. This should almost always be the 22nd of a month (YYYY-MM-22), unless you did an out of band blog post.
+ removal_milestone: "15.0" # The milestone when this feature is planned to be removed
+ removal_date: "2022-06-22" # This should almost always be the 22nd of a month (YYYY-MM-22), the date of the milestone release when this feature is planned to be removed.
+ body: | # Do not modify this line, instead modify the lines below.
The use of `fixup!` as a commit message to trigger draft status
of the associated Merge Request is generally unused, and can cause
confusion with other uses of the term. "Draft" is the preferred