File tree Expand file tree Collapse file tree 2 files changed +46
-0
lines changed Expand file tree Collapse file tree 2 files changed +46
-0
lines changed Original file line number Diff line number Diff line change
1
+ <!--
2
+ In order for a pull request to be considered for inclusion in a release branch
3
+ (release/x.y) after it has been cut, the pull request must have the following
4
+ information filled out in its description.
5
+
6
+ To draft a pull request using this template, append '&template=release.md' to
7
+ a pull request preview URL (the "Open a pull request" page), or use the
8
+ following URL template:
9
+
10
+ https://github.com/apple/swift/compare/main...<username>:swift:<my-branch>?expand=1&template=release.md
11
+ -->
12
+
13
+ * Explanation:
14
+ <!--
15
+ A description of the change. This can be brief, but it should be clear.
16
+ -->
17
+ * Scope:
18
+ <!--
19
+ An assessment of the impact/importance of the change. For example, is the
20
+ change a source-breaking language change?
21
+ -->
22
+ * Issues:
23
+ <!--
24
+ References to issues the change resolves, if any.
25
+ -->
26
+ * Original PR:
27
+ <!--
28
+ Link to the main branch version of this pull request.
29
+ -->
30
+ * Risk:
31
+ <!--
32
+ What is the (specific) risk to the release for taking this change?
33
+ -->
34
+ * Testing:
35
+ <!--
36
+ What specific testing has been done or needs to be done to further validate
37
+ any impact of this change?
38
+ -->
39
+ * Reviewers:
40
+ <!--
41
+ The code owners that reviewed the original PR. One or more code owners of
42
+ the impacted components should review the change. Technical review can be
43
+ delegated by a code owner or otherwise requested as deemed appropriate or
44
+ useful.
45
+ -->
46
+
File renamed without changes.
You can’t perform that action at this time.
0 commit comments