Remove Links header
What does this MR do?
This completes the deprecation of the Links
header in favour of the standard
Link
header. See: !33714 (merged)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Related to #220312 (closed)
Merge request reports
Activity
changed milestone to %14.0
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.
Category Reviewer Maintainer backend Małgorzata Ksionek ( @mksionek
) (UTC+2, 1 hour ahead of@alexkalderimis
)James Fargher ( @proglottis
) (UTC+12, 11 hours ahead of@alexkalderimis
)If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermarked the checklist item I have added/updated documentation, or it's not needed. (Is documentation required?) as completed
marked the checklist item I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) as completed
added 35 commits
-
22c25a93...26a202fd - 34 commits from branch
master
- b702e218 - Remove Links header
-
22c25a93...26a202fd - 34 commits from branch
added 19 commits
-
b702e218...651e2504 - 18 commits from branch
master
- 47203a78 - Remove Links header
-
b702e218...651e2504 - 18 commits from branch
added workflowin review label
requested review from @mksionek
assigned to @mksionek
marked the checklist item I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) as completed
removed [deprecated] Accepting merge requests label
Danger chooses you @proglottis! - Could you please give this MR its maintainer backend review?
requested review from @proglottis
assigned to @proglottis
enabled an automatic merge when the pipeline for f02b3a61 succeeds
removed review request for @mksionek
unassigned @proglottis
mentioned in commit ab70437a
added workflowstaging label and removed workflowin review label
added workflowcanary label and removed workflowstaging label
added workflowproduction label and removed workflowcanary label
mentioned in issue #220312 (closed)
added releasedcandidate label
mentioned in merge request kubitus-project/kubitus-installer!39 (merged)
added releasedpublished label and removed releasedcandidate label
mentioned in merge request !68346 (merged)
added 1 deleted label and removed devopscreate label
added devopsmanage label and removed 1 deleted label