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
+4-4
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ For more information about making contributions to the Swift project in general
10
10
11
11
## Reporting issues
12
12
13
-
Issues are tracked using [SwiftPM GitHub Issue Tracker](https://github.com/apple/swift-package-manager/issues).
13
+
Issues are tracked using [SwiftPM GitHub Issue Tracker](https://github.com/swiftlang/swift-package-manager/issues).
14
14
15
15
Fill the following fields:
16
16
@@ -37,7 +37,7 @@ generated and the Xcode build log.
37
37
38
38
## Setting up the development environment
39
39
40
-
First, clone a copy of SwiftPM code from https://github.com/apple/swift-package-manager.
40
+
First, clone a copy of SwiftPM code from https://github.com/swiftlang/swift-package-manager.
41
41
42
42
If you are preparing to make a contribution you should fork the repository first and clone the fork which will make opening Pull Requests easier. See "Creating Pull Requests" section below.
43
43
@@ -314,7 +314,7 @@ Note there are several Linux and Swift versions options to choose from, e.g.:
Copy file name to clipboardExpand all lines: Documentation/libSwiftPM.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -10,12 +10,12 @@ A subset of `libSwiftPM` that includes only the data model (without SwiftPM's
10
10
build system) is available as `libSwiftPMDataModel`. Any one client should
11
11
depend on one or the other, but not both.
12
12
13
-
The SwiftPM repository contains an [example](https://github.com/apple/swift-package-manager/tree/master/Examples/package-info) that demonstrates the use of
13
+
The SwiftPM repository contains an [example](https://github.com/swiftlang/swift-package-manager/tree/master/Examples/package-info) that demonstrates the use of
14
14
`libSwiftPM` in a Swift package. Use the following commands to run the example
Copy file name to clipboardExpand all lines: README.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ We’ve designed the system to make it easy to share packages on services like G
6
6
7
7
Swift Package Manager includes a build system that can build for macOS and Linux. Starting with Xcode 11, Xcode integrates with SwiftPM to provide support for including packages in iOS, macOS, watchOS, and tvOS applications.
8
8
9
-
The [SourceKit-LSP](https://github.com/apple/sourcekit-lsp) project leverages libSwiftPM and provides [Language Server Protocol](https://langserver.org/) implementation for editors that support LSP.
9
+
The [SourceKit-LSP](https://github.com/swiftlang/sourcekit-lsp) project leverages libSwiftPM and provides [Language Server Protocol](https://langserver.org/) implementation for editors that support LSP.
10
10
11
11
---
12
12
@@ -73,7 +73,7 @@ The Swift package manager uses [llbuild](https://github.com/apple/swift-llbuild)
73
73
If you have any trouble with the package manager, help is available. We recommend:
74
74
75
75
* The [Swift Forums](https://forums.swift.org/c/development/swiftpm/),
Copy file name to clipboardExpand all lines: Sources/PackageCollectionsModel/Formats/v1.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ To begin, define the top-level metadata about the collection:
28
28
Each item in the `packages` array is a package object with the following properties:
29
29
30
30
*`url`: The URL of the package. Currently only Git repository URLs are supported. URL should be HTTPS and may contain `.git` suffix.
31
-
*`identity`: The [identity](https://github.com/apple/swift-package-manager/blob/main/Documentation/PackageRegistry/Registry.md#36-package-identification) of the package if published to registry. **Optional.**
31
+
*`identity`: The [identity](https://github.com/swiftlang/swift-package-manager/blob/main/Documentation/PackageRegistry/Registry.md#36-package-identification) of the package if published to registry. **Optional.**
32
32
*`summary`: A description of the package. **Optional.**
33
33
*`keywords`: An array of keywords that the package is associated with. **Optional.**
34
34
*`readmeURL`: The URL of the package's README. **Optional.**
@@ -102,7 +102,7 @@ A version object has metadata extracted from `Package.swift` and optionally addi
*`author`: The package version's author. **Optional.**
104
104
*`name`: The author of the package version.
105
-
*`signer`: The signer of the package version. **Optional.** Refer to [documentation](https://github.com/apple/swift-package-manager/blob/main/Documentation/PackageRegistry/PackageRegistryUsage.md#package-signing) on package signing for details.
105
+
*`signer`: The signer of the package version. **Optional.** Refer to [documentation](https://github.com/swiftlang/swift-package-manager/blob/main/Documentation/PackageRegistry/PackageRegistryUsage.md#package-signing) on package signing for details.
106
106
*`type`: The signer type. Currently the only valid value is `ADP` (Apple Developer Program).
107
107
*`commonName`: The common name of the signing certificate's subject.
108
108
*`organizationalUnitName`: The organizational unit name of the signing certificate's subject.
@@ -111,15 +111,15 @@ A version object has metadata extracted from `Package.swift` and optionally addi
111
111
112
112
##### Version-specific manifests
113
113
114
-
Package collection generators should include data from the "default" manifest `Package.swift` as well as [version-specific manifest(s)](https://github.com/apple/swift-package-manager/blob/main/Documentation/Usage.md#version-specific-manifest-selection).
114
+
Package collection generators should include data from the "default" manifest `Package.swift` as well as [version-specific manifest(s)](https://github.com/swiftlang/swift-package-manager/blob/main/Documentation/Usage.md#version-specific-manifest-selection).
115
115
116
116
The keys of the `manifests` map are Swift tools (semantic) versions:
117
117
* For `Package.swift`, the tools version specified in `Package.swift` should be used.
118
118
* For version-specific manifests, the tools version specified in the filename should be used. For example, for `[email protected]` it would be `4.2`. The tools version in the manifest must match that in the filename.
119
119
120
120
##### Version-specific tags
121
121
122
-
[Version-specific tags](https://github.com/apple/swift-package-manager/blob/main/Documentation/Usage.md#version-specific-tag-selection) are not
122
+
[Version-specific tags](https://github.com/swiftlang/swift-package-manager/blob/main/Documentation/Usage.md#version-specific-tag-selection) are not
Copy file name to clipboardExpand all lines: Sources/PackageDescription/PackageDescription.docc/PackageDescription.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ The package manifest also allows you to define executable products, as well as p
40
40
41
41
For more information about adding a package dependency to your app project and creating Swift packages with Xcode, see [Adding Package Dependencies to Your App](https://developer.apple.com/documentation/xcode/adding-package-dependencies-to-your-app), [Creating a Standalone Swift Package with Xcode](https://developer.apple.com/documentation/xcode/creating-a-standalone-swift-package-with-xcode), and [Swift Packages](https://developer.apple.com/documentation/xcode/swift-packages).
42
42
43
-
Support for Swift packages in Xcode builds on the open-source Swift Package Manager project. To learn more about the Swift Package Manager, visit [Swift.org](https://www.swift.org/package-manager/) and the Swift Package Manager repository on [GitHub](https://github.com/apple/swift-package-manager).
43
+
Support for Swift packages in Xcode builds on the open-source Swift Package Manager project. To learn more about the Swift Package Manager, visit [Swift.org](https://www.swift.org/package-manager/) and the Swift Package Manager repository on [GitHub](https://github.com/swiftlang/swift-package-manager).
/// * Otherwise, if the "include" directory only contains header files and no other subdirectory:
64
64
/// Generates: `umbrella "path/to/include"`
65
65
///
66
-
/// These rules are documented at https://github.com/apple/swift-package-manager/blob/master/Documentation/Usage.md#creating-c-language-targets. To avoid breaking existing packages, do not change the semantics here without making any change conditional on the tools version of the package that defines the module.
66
+
/// These rules are documented at https://github.com/swiftlang/swift-package-manager/blob/master/Documentation/Usage.md#creating-c-language-targets. To avoid breaking existing packages, do not change the semantics here without making any change conditional on the tools version of the package that defines the module.
67
67
///
68
68
/// Note that a module map generator doesn't require a module to already have been instantiated; it can operate on information that will later be used to instantiate a module.
69
69
publicstructModuleMapGenerator{
@@ -89,7 +89,7 @@ public struct ModuleMapGenerator {
89
89
90
90
/// Inspects the file system at the public-headers directory with which the module map generator was instantiated, and returns the type of module map that applies to that directory. This function contains all of the heuristics that implement module map policy for package targets; other functions just use the results of this determination.
// The following rules are documented at https://github.com/apple/swift-package-manager/blob/master/Documentation/Usage.md#creating-c-language-targets. To avoid breaking existing packages, do not change the semantics here without making any change conditional on the tools version of the package that defines the module.
92
+
// The following rules are documented at https://github.com/swiftlang/swift-package-manager/blob/master/Documentation/Usage.md#creating-c-language-targets. To avoid breaking existing packages, do not change the semantics here without making any change conditional on the tools version of the package that defines the module.
0 commit comments