1<!-- Thanks for sending a pull request!
2
3If you already have a well-structured git commit message, chances are GitHub
4set the title and description of this PR to the git commit message subject and
5body, respectively. If so, you may delete these instructions and submit your PR.
6
7If this is your first time, please read our contributor guide:
8https://github.com/linkerd/linkerd2/blob/main/CONTRIBUTING.md
9
10The title and description of your Pull Request should match the git commit
11subject and body, respectively. Git commit messages are structured as follows:
12
13```
14Subject
15
16Problem
17
18Solution
19
20Validation
21
22Fixes #[GitHub issue ID]
23
24DCO Sign off
25```
26
27Example git commit message:
28
29```
30Introduce Pull Request Template
31
32GitHub's community guidelines recommend a pull request template, the repo was
33lacking one.
34
35Introduce a `PULL_REQUEST_TEMPLATE.md` file.
36
37Once merged, the
38[Community profile checklist](https://github.com/linkerd/linkerd2/community)
39should indicate the repo now provides a pull request template.
40
41Fixes #3321
42
43Signed-off-by: Jane Smith <jane.smith@example.com>
44```
45
46Note the git commit message subject becomes the pull request title.
47
48For more details around git commits, see the section on Committing in our
49contributor guide:
50https://github.com/linkerd/linkerd2/blob/main/CONTRIBUTING.md#committing
51-->
View as plain text