Changes for .gitlab/merge_request_templates/Default.md: 3 added lines, 5 removed lines.
Original line number
Diff line number
Diff line
@@ -2,9 +2,9 @@
## Why is this change being made?
> :bulb: **Provide a detailed answer to the question on *why* this change is being proposed, in accordance with our value of [Transparency][transparency].**
> :bulb: **Provide a detailed answer to the question on *why* this change is being proposed, in accordance with our value of Transparency.**
>
> Please add the details saying [why, not just what][say-why-not-just-what] in this section. Example: `We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.`
> Please add the details saying why, not just what in this section. Example: `We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.`
CHANGEME
@@ -13,7 +13,7 @@ CHANGEME
**Please verify the check list and ensure to tick them off before the MR is merged.**
-[ ] Provided a concise title for this [Merge Request (MR)][mr]
-[ ] Added a description to this MR explaining the reasons for the proposed change, per [**say why, not just what**][say-why-not-just-what]
- [ ] Added a description to this MR explaining the reasons for the proposed change, per **say why, not just what**
- Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is [SAFE][SAFE]
- [ ] Assign reviewers for this MR to the correct
- The [when to get approval][when-to-get-approval] handbook section explains when [DRI][dri] approval is required
Changes for .gitlab/merge_request_templates/Handbook-Operations.md: 3 added lines, 5 removed lines.
Original line number
Diff line number
Diff line
@@ -3,8 +3,8 @@
## Why is this change being made?
> :bulb: **Provide a detailed answer to the question on *why* this change is being proposed, in accordance with our value of [Transparency][transparency].**
> Please add the details saying [why, not just what][say-why-not-just-what] in this section.
> :bulb: **Provide a detailed answer to the question on *why* this change is being proposed, in accordance with our value of Transparency.**
> Please add the details saying why, not just what in this section.
@@ -17,7 +17,7 @@
**Please verify the check list and ensure to tick them off before the MR is merged.**
-[ ] Provided a concise title for this [Merge Request (MR)][mr]
-[ ] Added a description to this MR explaining the reasons for the proposed change, per [**say why, not just what**][say-why-not-just-what]
- [ ] Added a description to this MR explaining the reasons for the proposed change, per **say why, not just what**
- Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is [SAFE][SAFE]
-[ ] Assign reviewers for this MR to a code owner, typically [a handbook maintainer][hb-maintainer]
- If you're unsure, please mention [the handbook owner][hb-dri]
Changes for assets/includes/engineering-careers/development-intermediate-leadership-competency.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -9,7 +9,7 @@
* Adheres to the [GitLab communication guidelines](/handbook/communication/).
* Seeks assistance in clearly managing expectations around the delivery of their work.
* Delivers work given clear requirements within the context of their team.
* Makes responsible decisions in alignment with GitLab's [CREDIT values](/handbook/values/) by ideating options, identifying the consequences of each option, evaluating trade-offs and seeking advice from others when necessary.
* Makes responsible decisions in alignment with GitLab's CREDIT values by ideating options, identifying the consequences of each option, evaluating trade-offs and seeking advice from others when necessary.
* Thinks critically by understanding why something needs to be done, determining the root cause of the problem, identifying objectives and examining previous efforts.
* Remains calm under pressure.
* Demonstrates knowledge about how their work aligns with their [Product section, stages, groups and categories](/handbook/product/categories/).
Changes for assets/includes/engineering-careers/development-intermediate-values-competency.md: 1 added line, 1 removed line.
Original line number
Diff line number
Diff line
@@ -13,5 +13,5 @@
* Prioritizes work by following [GitLab Priority and Severity label](/handbook/product-development/how-we-work/issue-triage/#priority) guidelines, focusing on high-value activities, completing tasks with the earliest deadlines, and when in doubt, seek clarification regarding the priorities.
* Balances short term gains and long term benefit with team's help. For example, advocating for technical debt resolution and understanding the opportunity cost in comparison to a quick customer win.
* Creates proposals for their team that clearly defines the problem, offers alternatives, and proposes a solution. These proposals are small in scope, looking to address problems with a small surface area.
* Incorporates [Iteration](/handbook/values/#iteration) in every aspect of your job (examples: development, issue creation, planning, process improvements)
* Incorporates Iteration in every aspect of your job (examples: development, issue creation, planning, process improvements)
* Provides context and background on projects and issues so that those with no prior knowledge are able to contribute to the discussion.