You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+2-15
Original file line number
Diff line number
Diff line change
@@ -84,22 +84,9 @@ Once you've pushed your branch, you should see an option on this repository's pa
84
84
85
85
## Opening a PR for Release Branch
86
86
87
-
In order for a pull request to be considered for inclusion in a release branch (e.g. `release/6.0`) after it has been cut, it must meet the following requirements:
87
+
See the [dedicated section][section] on the Swift project website.
88
88
89
-
1. The title of the PR should start with the tag `[{swift version number}]`. For example, `[6.0]` for the Swift 6.0 release branch.
90
-
91
-
1.[This][form] should be filled out in the description of the PR.
92
-
To use this template when creating a PR, append the `template=release.md`
-`CanImportExprSyntax` and `CanImportVersionInfoSyntax`
136
-
- Description: Instead of parsing `canImport` inside `#if` directives as a special expression node, parse it as a functionc call expression. This is in-line with how the `swift(>=6.0)` and `compiler(>=6.0)` directives are parsed.
136
+
- Description: Instead of parsing `canImport` inside `#if` directives as a special expression node, parse it as a function call expression. This is in-line with how the `swift(>=6.0)` and `compiler(>=6.0)` directives are parsed.
-`Error` protocol now has an `asDiagnostics(at:)` method.
15
+
- Description: This method translates an error into one or more diagnostics, recognizing `DiagnosticsError` and `DiagnosticMessage` instances or providing its own `Diagnostic` as needed.
0 commit comments