Skip to content
Snippets Groups Projects
Commit 278e4dd2 authored by Hanif Smith-Watson's avatar Hanif Smith-Watson
Browse files

Cleanse irrelevant in redirects.yml

parent f69e3f2b
No related branches found
No related tags found
Loading
...@@ -8,4 +8,4 @@ retrospectives]. ...@@ -8,4 +8,4 @@ retrospectives].
[retros]: https://gitlab.com/gl-retrospectives/create-stage/<%= group_slug %>/issues?scope=all&utf8=%E2%9C%93&state=all&label_name[]=retrospective [retros]: https://gitlab.com/gl-retrospectives/create-stage/<%= group_slug %>/issues?scope=all&utf8=%E2%9C%93&state=all&label_name[]=retrospective
[GitLab retrospective]: /handbook/engineering/workflow/#retrospective [GitLab retrospective]: /handbook/engineering/workflow/#retrospective
[team retrospectives]: /handbook/engineering/management/team-retrospectives/ [team retrospectives]: /handbook/engineering/management/group-retrospectives/
...@@ -136,7 +136,7 @@ backend component: ...@@ -136,7 +136,7 @@ backend component:
- When both frontend and backend DRIs are assigned, consider hosting a small kickoff discussion. - When both frontend and backend DRIs are assigned, consider hosting a small kickoff discussion.
- When the backend work is merged and verified add [the ~"backend complete" label](#using-the-backend-complete-label). - When the backend work is merged and verified add [the ~"backend complete" label](#using-the-backend-complete-label).
We value [velocity over predictability](/handbook/engineering/principles/#velocity-over-predictability) We value [velocity over predictability](/handbook/engineering/development/principles/)
so use your own judgement on whether you should wait for your counterpart to so use your own judgement on whether you should wait for your counterpart to
get involved before proceeding with development. get involved before proceeding with development.
......
...@@ -12,7 +12,7 @@ description: "The Growth:Acquisition group works on feature enhancements and gro ...@@ -12,7 +12,7 @@ description: "The Growth:Acquisition group works on feature enhancements and gro
## Vision ## Vision
The Acquisition Group is part of the [Growth Stage]. We work on [connecting our users with our product value](/direction/growth/). The Acquisition Group is part of the [Growth Stage]. We work on [connecting our users with our product value](/handbook/marketing/growth/).
* I have a question. Who do I ask? * I have a question. Who do I ask?
...@@ -56,7 +56,7 @@ stable_counterparts(role_regexp: roles_regexp, direct_manager_role: direct_manag ...@@ -56,7 +56,7 @@ stable_counterparts(role_regexp: roles_regexp, direct_manager_role: direct_manag
Prioritization is a collaboration between Product, UX, Engineering, and Quality. Prioritization is a collaboration between Product, UX, Engineering, and Quality.
* We use the [ICE framework](/direction/growth/#growth-ideation-and-prioritization) for experiments * We use the [ICE framework](/handbook/marketing/growth/) for experiments
* We use [Priority](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels) * We use [Priority](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels)
and [Severity](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels) labels for bugs and [Severity](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels) labels for bugs
......
...@@ -12,7 +12,7 @@ description: "The Growth:Activation group works on feature enhancements and grow ...@@ -12,7 +12,7 @@ description: "The Growth:Activation group works on feature enhancements and grow
## Vision ## Vision
The Activation Group is part of the [Growth Stage]. We work on [connecting our users with our product value](/direction/growth/). The Activation Group is part of the [Growth Stage]. We work on [connecting our users with our product value](/handbook/marketing/growth/).
* I have a question. Who do I ask? * I have a question. Who do I ask?
...@@ -55,7 +55,7 @@ stable_counterparts(role_regexp: roles_regexp, direct_manager_role: direct_manag ...@@ -55,7 +55,7 @@ stable_counterparts(role_regexp: roles_regexp, direct_manager_role: direct_manag
Prioritization is a collaboration between Product, UX, and Engineering. Prioritization is a collaboration between Product, UX, and Engineering.
* We use the [ICE framework](/direction/growth/#growth-ideation-and-prioritization) for experiments. * We use the [ICE framework](/handbook/marketing/growth/) for experiments.
* We use [Priority](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels) * We use [Priority](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels)
and [Severity](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels) labels for bugs. and [Severity](https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels) labels for bugs.
......
...@@ -29,7 +29,7 @@ Teams focus on validating ideas with data and provide development input into two ...@@ -29,7 +29,7 @@ Teams focus on validating ideas with data and provide development input into two
- [Continuous onboarding](https://gitlab.com/gitlab-org/gitlab/-/issues/323176) - [Continuous onboarding](https://gitlab.com/gitlab-org/gitlab/-/issues/323176)
We work on the issues prioritized by our product teams including running [experiments](/handbook/engineering/development/growth/experimentation/) on GitLab.com. We work on the issues prioritized by our product teams including running [experiments](/handbook/engineering/development/growth/experimentation/) on GitLab.com.
More information on priorities can be found on the [Growth direction](/direction/growth/) page. More information on priorities can be found on the [Growth direction](/handbook/marketing/growth/) page.
Growth stage teams have Fullstack Engineers. Growth stage teams have Fullstack Engineers.
The reason for this is that the Growth stage has a need for both Frontend and Backend skill-sets, The reason for this is that the Growth stage has a need for both Frontend and Backend skill-sets,
...@@ -37,7 +37,7 @@ but as a small team, has optimized for team member efficiency to adopt the Fulls ...@@ -37,7 +37,7 @@ but as a small team, has optimized for team member efficiency to adopt the Fulls
Some useful links to see how and what we are working on include: Some useful links to see how and what we are working on include:
- [Growth direction](/direction/growth/) - [Growth direction](/handbook/marketing/growth/)
- [Growth group issues](https://gitlab.com/groups/gitlab-org/-/boards/1392106?&label_name%5B%5D=devops%3A%3Agrowth) - [Growth group issues](https://gitlab.com/groups/gitlab-org/-/boards/1392106?&label_name%5B%5D=devops%3A%3Agrowth)
- [Experimentation](experimentation/) - [Experimentation](experimentation/)
- [GLEX](https://gitlab.com/gitlab-org/ruby/gems/gitlab-experiment) - [GLEX](https://gitlab.com/gitlab-org/ruby/gems/gitlab-experiment)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment