Migrate URLs in documentation/comments/etc. from /apple/ to /swiftlang/. (#596)

This PR moves all references to URLs under https://github.com/apple/ to
https://github.com/swiftlang/.

### Checklist:

- [x] Code and documentation should follow the style of the [Style
Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md).
- [x] If public symbols are renamed or modified, DocC references should
be updated.

Author: grynspan

CONTRIBUTING.md

@@ -18,12 +18,12 @@ discussion prior to being accepted.
 
 To learn how to write tests using the testing library, rather than how to
 contribute to the testing library itself, see
-[Getting Started](https://github.com/apple/swift-testing/tree/main/Sources/Testing/Testing.docc/TemporaryGettingStarted.md).
+[Getting Started](https://github.com/swiftlang/swift-testing/tree/main/Sources/Testing/Testing.docc/TemporaryGettingStarted.md).
 
 ## Reporting issues
 
 Issues are tracked using the testing library's
-[GitHub Issue Tracker](https://github.com/apple/swift-testing/issues).
+[GitHub Issue Tracker](https://github.com/swiftlang/swift-testing/issues).
 
 Fill in the fields of the relevant template form offered on that page when
 creating new issues. For bug report issues, please include a minimal example
@@ -34,7 +34,7 @@ hosting service.
 ## Setting up the development environment
 
 First, clone the Swift Testing repository from
-[https://github.com/apple/swift-testing](https://github.com/apple/swift-testing).
+[https://github.com/swiftlang/swift-testing](https://github.com/swiftlang/swift-testing).
 
 If you're preparing to make a contribution, you should fork the repository first
 and clone the fork which will make opening PRs easier.
@@ -142,7 +142,7 @@ test --help` to view the usage documentation.
 
 ## Creating Pull Requests (PRs)
 
-1. Fork [https://github.com/apple/swift-testing](https://github.com/apple/swift-testing).
+1. Fork [https://github.com/swiftlang/swift-testing](https://github.com/swiftlang/swift-testing).
 1. Clone a working copy of your fork.
 1. Create a new branch.
 1. Make your code changes.

Dockerfile

@@ -9,7 +9,7 @@
 FROM swiftlang/swift:nightly-main-jammy
 
 # Set up the current build user in the same way done in the Swift.org CI system:
-# https://github.com/apple/swift-docker/blob/main/swift-ci/master/ubuntu/22.04/Dockerfile
+# https://github.com/swiftlang/swift-docker/blob/main/swift-ci/master/ubuntu/22.04/Dockerfile
 
 RUN groupadd -g 998 build-user && \
     useradd -m -r -u 998 -g build-user build-user

Documentation/CMake.md

@@ -8,7 +8,7 @@ Add Swift Testing to your project using the standard `FetchContent` or
 ```cmake
 include(FetchContent)
 FetchContent_Declare(SwiftTesting
-  GIT_REPOSITORY https://github.com/apple/swift-testing.git
+  GIT_REPOSITORY https://github.com/swiftlang/swift-testing.git
   GIT_TAG main)
 FetchContent_MakeAvailable(SwiftTesting)
 ```

Documentation/Proposals/0000-proposal-template.md

@@ -3,10 +3,10 @@
 * Proposal: [SWT-NNNN](NNNN-filename.md)
 * Authors: [Author 1](https://github.com/author1), [Author 2](https://github.com/author2)
 * Status: **Awaiting implementation** or **Awaiting review**
-* Bug: _if applicable_ [apple/swift-testing#NNNNN](https://github.com/apple/swift-testing/issues/NNNNN)
-* Implementation: [apple/swift-testing#NNNNN](https://github.com/apple/swift-testing/pull/NNNNN)
+* Bug: _if applicable_ [swiftlang/swift-testing#NNNNN](https://github.com/swiftlang/swift-testing/issues/NNNNN)
+* Implementation: [swiftlang/swift-testing#NNNNN](https://github.com/swiftlang/swift-testing/pull/NNNNN)
 * Previous Proposal: _if applicable_ [SWT-XXXX](XXXX-filename.md)
-* Previous Revision: _if applicable_ [1](https://github.com/apple/swift-testing/blob/...commit-ID.../Documentation/Proposals/NNNN-filename.md)
+* Previous Revision: _if applicable_ [1](https://github.com/swiftlang/swift-testing/blob/...commit-ID.../Documentation/Proposals/NNNN-filename.md)
 * Review: ([pitch](https://forums.swift.org/...))
 
 When filling out this template, you should delete or replace all of the text
@@ -146,7 +146,7 @@ the current proposal. It's important to make focused, self-contained proposals
 that can be incrementally implemented and reviewed, but it's also good when
 proposals feel "complete" rather than leaving significant gaps in their design.
 An an example from the Swift project, when
-[SE-0193](https://github.com/apple/swift-evolution/blob/main/proposals/0193-cross-module-inlining-and-specialization.md)
+[SE-0193](https://github.com/swiftlang/swift-evolution/blob/main/proposals/0193-cross-module-inlining-and-specialization.md)
 introduced the `@inlinable` attribute, it also included the `@usableFromInline`
 attribute so that declarations used in inlinable functions didn't have to be
 `public`. This was a relatively small addition to the proposal which avoided

Documentation/Proposals/0001-refactor-bug-inits.md

@@ -3,7 +3,7 @@
 * Proposal: [SWT-0001](0001-refactor-bug-inits.md)
 * Authors: [Jonathan Grynspan](https://github.com/grynspan)
 * Status: **Accepted**
-* Implementation: [apple/swift-testing#401](https://github.com/apple/swift-testing/pull/401)
+* Implementation: [swiftlang/swift-testing#401](https://github.com/swiftlang/swift-testing/pull/401)
 * Review: ([pitch](https://forums.swift.org/t/pitch-dedicated-bug-functions-for-urls-and-ids/71842)), ([acceptance](https://forums.swift.org/t/swt-0001-dedicated-bug-functions-for-urls-and-ids/71842/2))
 
 ## Introduction

Documentation/Proposals/0002-json-abi.md

@@ -3,8 +3,8 @@
 * Proposal: [SWT-0002](0002-json-abi.md)
 * Authors: [Jonathan Grynspan](https://github.com/grynspan)
 * Status: **Accepted**
-* Implementation: [apple/swift-testing#383](https://github.com/apple/swift-testing/pull/383),
-  [apple/swift-testing#402](https://github.com/apple/swift-testing/pull/402)
+* Implementation: [swiftlang/swift-testing#383](https://github.com/swiftlang/swift-testing/pull/383),
+  [swiftlang/swift-testing#402](https://github.com/swiftlang/swift-testing/pull/402)
 * Review: ([pitch](https://forums.swift.org/t/pitch-a-stable-json-based-abi-for-tools-integration/72627)), ([acceptance](https://forums.swift.org/t/pitch-a-stable-json-based-abi-for-tools-integration/72627/4))
 
 ## Introduction

Documentation/Proposals/0003-make-serialized-trait-api.md

@@ -4,7 +4,7 @@
 * Authors: [Dennis Weissmann](https://github.com/dennisweissmann)
 * Status: **Accepted**
 * Implementation: 
-[apple/swift-testing#535](https://github.com/apple/swift-testing/pull/535)
+[swiftlang/swift-testing#535](https://github.com/swiftlang/swift-testing/pull/535)
 * Review: 
 ([pitch](https://forums.swift.org/t/pitch-make-serialized-trait-public-api/73147)),
 ([acceptance](https://forums.swift.org/t/pitch-make-serialized-trait-public-api/73147/5))

Documentation/Proposals/0004-constrain-the-granularity-of-test-time-limit-durations.md

@@ -5,7 +5,7 @@
 * Authors: [Dennis Weissmann](https://github.com/dennisweissmann)
 * Status: **Accepted**
 * Implementation: 
-[apple/swift-testing#534](https://github.com/apple/swift-testing/pull/534)
+[swiftlang/swift-testing#534](https://github.com/swiftlang/swift-testing/pull/534)
 * Review: 
 ([pitch](https://forums.swift.org/t/pitch-constrain-the-granularity-of-test-time-limit-durations/73146)),
 ([acceptance](https://forums.swift.org/t/pitch-constrain-the-granularity-of-test-time-limit-durations/73146/3))

Documentation/README.md

@@ -13,36 +13,36 @@ See https://swift.org/CONTRIBUTORS.txt for Swift project authors
 ## API and usage guides
 
 The detailed documentation for Swift Testing can be found on the
-[Swift Package Index](https://swiftpackageindex.com/apple/swift-testing/main/documentation/testing).
+[Swift Package Index](https://swiftpackageindex.com/swiftlang/swift-testing/main/documentation/testing).
 There, you can delve into comprehensive guides, tutorials, and API references to
 make the most out of this package.
 
-This documentation is generated using [DocC](https://github.com/apple/swift-docc)
+This documentation is generated using [DocC](https://github.com/swiftlang/swift-docc)
 and is derived from symbol documentation in this project's source code as well
 as supplemental content located in the
-[`Sources/Testing/Testing.docc/`](https://github.com/apple/swift-testing/tree/main/Sources/Testing/Testing.docc)
+[`Sources/Testing/Testing.docc/`](https://github.com/swiftlang/swift-testing/tree/main/Sources/Testing/Testing.docc)
 directory.
 
 ## Vision document
 
-The [Vision document](https://github.com/apple/swift-evolution/blob/main/visions/swift-testing.md)
+The [Vision document](https://github.com/swiftlang/swift-evolution/blob/main/visions/swift-testing.md)
 for Swift Testing offers a comprehensive discussion of the project's design
 principles and goals. 
 
 ## Development and contribution
 
-- The top-level [`README`](https://github.com/apple/swift-testing/blob/main/README.md)
+- The top-level [`README`](https://github.com/swiftlang/swift-testing/blob/main/README.md)
   gives a high-level overview of the project, shows current CI status, lists the
   support status of various platforms, and more.
-- [Contributing](https://github.com/apple/swift-testing/blob/main/CONTRIBUTING.md)
+- [Contributing](https://github.com/swiftlang/swift-testing/blob/main/CONTRIBUTING.md)
   provides guidance for developing and making project contributions.
-- [Style Guide](https://github.com/apple/swift-testing/blob/main/Documentation/StyleGuide.md)
+- [Style Guide](https://github.com/swiftlang/swift-testing/blob/main/Documentation/StyleGuide.md)
   describes this project's guidelines for code and documentation style.
-- [SPI groups in Swift Testing](https://github.com/apple/swift-testing/blob/main/Documentation/SPI.md)
+- [SPI groups in Swift Testing](https://github.com/swiftlang/swift-testing/blob/main/Documentation/SPI.md)
   describes when and how the testing library uses Swift SPI.
 
 ## Project maintenance
 
-- The [Releases](https://github.com/apple/swift-testing/blob/main/Documentation/Releases.md)
+- The [Releases](https://github.com/swiftlang/swift-testing/blob/main/Documentation/Releases.md)
   document describes the process of creating and publishing a new release of
   Swift Testing — a task which may be performed by project administrators.

Documentation/Releases.md

@@ -49,8 +49,8 @@ be updated so that the release can be used as a package dependency:
    update the line:
 
     ```diff
-    -  .package(url: "https://github.com/apple/swift-testing.git", branch: "main"),
-    +  .package(url: "https://github.com/apple/swift-testing.git", from: "x.y.z"),
+    -  .package(url: "https://github.com/swiftlang/swift-testing.git", branch: "main"),
+    +  .package(url: "https://github.com/swiftlang/swift-testing.git", from: "x.y.z"),
     ```
 
 The repository's local state is now updated. To commit it to your branch, run
@@ -94,7 +94,7 @@ git tag x.y.z
 git push -u origin x.y.z
 ```
 
-The release is now live and publicly visible [here](https://github.com/apple/swift-testing/tags).
+The release is now live and publicly visible [here](https://github.com/swiftlang/swift-testing/tags).
 Developers using Swift Package Manager and listing Swift Testing as a dependency
 will automatically update to it.
 

Documentation/StyleGuide.md

@@ -140,12 +140,12 @@ Begin topic group headings inside types with a noun or noun phrase.
 
 The macro target of this package produces a number of different compile-time
 diagnostics. These diagnostics should be written according to the Swift style
-guide for compiler diagnostics [here](https://github.com/apple/swift/blob/main/docs/Diagnostics.md).
+guide for compiler diagnostics [here](https://github.com/swiftlang/swift/blob/main/docs/Diagnostics.md).
 
 ### Documentation
 
 Documentation for the testing library should follow the
-[Swift Book style guide](https://github.com/apple/swift-book/blob/main/Style.md)
+[Swift Book style guide](https://github.com/swiftlang/swift-book/blob/main/Style.md)
 and [Apple Style Guide](https://support.apple.com/guide/applestyleguide/) as
 contextually appropriate.
 

Documentation/Vision.md

@@ -7,7 +7,7 @@ automated testing to identify software defects. Better APIs and tools for
 testing can greatly improve a platform’s quality. Below, we propose a new API
 direction for testing in Swift.
 
-Click [here](https://github.com/apple/swift-evolution/blob/main/visions/swift-testing.md)
+Click [here](https://github.com/swiftlang/swift-evolution/blob/main/visions/swift-testing.md)
 to view the complete vision document for Swift Testing, which has been accepted
 by the Swift Language Steering Group and is now hosted in the
-[swift-evolution](https://github.com/apple/swift-evolution) repository.
+[swift-evolution](https://github.com/swiftlang/swift-evolution) repository.

NOTICE.txt

@@ -4,7 +4,7 @@
 
 Please visit the Swift Testing web site for more information:
 
-  * https://github.com/apple/swift-testing
+  * https://github.com/swiftlang/swift-testing
 
 Copyright (c) 2023 Apple Inc. and the Swift project authors
 

Package.swift

@@ -140,7 +140,7 @@ extension Array where Element == PackageDescription.SwiftSetting {
   ///
   /// These leverage a pseudo-experimental feature in the Swift compiler for
   /// setting availability definitions, which was added in
-  /// [apple/swift#65218](https://github.com/apple/swift/pull/65218).
+  /// [swift#65218](https://github.com/swiftlang/swift/pull/65218).
   private static var availabilityMacroSettings: Self {
     [
       .enableExperimentalFeature("AvailabilityMacro=_mangledTypeNameAPI:macOS 11.0, iOS 14.0, watchOS 7.0, tvOS 14.0"),

README.md

@@ -120,11 +120,11 @@ incrementally, at your own pace.
 > for details about stable release plans.
 
 Detailed documentation for Swift Testing can be found on the
-[Swift Package Index](https://swiftpackageindex.com/apple/swift-testing/main/documentation/testing).
+[Swift Package Index](https://swiftpackageindex.com/swiftlang/swift-testing/main/documentation/testing).
 There, you can delve into comprehensive guides, tutorials, and API references to
 make the most out of this package. To try it yourself, see
-[Getting Started](https://swiftpackageindex.com/apple/swift-testing/main/documentation/testing/temporarygettingstarted).
+[Getting Started](https://swiftpackageindex.com/swiftlang/swift-testing/main/documentation/testing/temporarygettingstarted).
 
 Other documentation resources for this project can be found in the
-[README](https://github.com/apple/swift-testing/blob/main/Documentation/README.md) 
+[README](https://github.com/swiftlang/swift-testing/blob/main/Documentation/README.md) 
 of the `Documentation/` subdirectory.

Sources/Testing/ABI/EntryPoints/EntryPoint.swift

@@ -559,7 +559,7 @@ private func _writeJSONLine(_ json: UnsafeRawBufferPointer, to file: borrowing F
   if _slowPath(json.contains(where: isASCIINewline)) {
 #if DEBUG
     let message = Event.ConsoleOutputRecorder.warning(
-      "JSON encoder produced one or more newline characters while encoding an event to JSON. Please file a bug report at https://github.com/apple/swift-testing/issues/new",
+      "JSON encoder produced one or more newline characters while encoding an event to JSON. Please file a bug report at https://github.com/swiftlang/swift-testing/issues/new",
       options: .for(.stderr)
     )
 #if SWT_TARGET_OS_APPLE

Sources/Testing/Events/Clock.swift

@@ -27,7 +27,7 @@ extension Test {
         // that of the Swift Clock API, so we don't use `SuspendingClock`
         // directly on them and instead derive a value from platform-specific
         // API. SuspendingClock corresponds to CLOCK_UPTIME_RAW on Darwin.
-        // SEE: https://github.com/apple/swift/blob/main/stdlib/public/Concurrency/Clock.cpp
+        // SEE: https://github.com/swiftlang/swift/blob/main/stdlib/public/Concurrency/Clock.cpp
         var uptime = timespec()
         _ = clock_gettime(CLOCK_UPTIME_RAW, &uptime)
         return TimeValue(uptime)

Sources/Testing/Events/TimeValue.swift

@@ -76,7 +76,7 @@ extension TimeValue: Codable {}
 extension TimeValue: CustomStringConvertible {
   var description: String {
 #if os(WASI)
-    // BUG: https://github.com/apple/swift/issues/72398
+    // BUG: https://github.com/swiftlang/swift/issues/72398
     return String(describing: Duration(self))
 #else
     let (secondsFromAttoseconds, attosecondsRemaining) = attoseconds.quotientAndRemainder(dividingBy: 1_000_000_000_000_000_000)

Sources/Testing/ExitTests/WaitFor.swift

@@ -32,7 +32,7 @@ private func _blockAndWait(for pid: pid_t) throws -> ExitCondition {
       case .init(CLD_KILLED), .init(CLD_DUMPED):
         return .signal(siginfo.si_status)
       default:
-        throw SystemError(description: "Unexpected siginfo_t value. Please file a bug report at https://github.com/apple/swift-testing/issues/new and include this information: \(String(reflecting: siginfo))")
+        throw SystemError(description: "Unexpected siginfo_t value. Please file a bug report at https://github.com/swiftlang/swift-testing/issues/new and include this information: \(String(reflecting: siginfo))")
       }
     } else if case let errorCode = swt_errno(), errorCode != EINTR {
       throw CError(rawValue: errorCode)
@@ -164,7 +164,7 @@ func wait(for pid: pid_t) async throws -> ExitCondition {
       // we add this continuation to the dictionary, then it will simply loop
       // and report the status again.
       let oldContinuation = childProcessContinuations.updateValue(continuation, forKey: pid)
-      assert(oldContinuation == nil, "Unexpected continuation found for PID \(pid). Please file a bug report at https://github.com/apple/swift-testing/issues/new")
+      assert(oldContinuation == nil, "Unexpected continuation found for PID \(pid). Please file a bug report at https://github.com/swiftlang/swift-testing/issues/new")
 
       // Wake up the waiter thread if it is waiting for more child processes.
       _ = pthread_cond_signal(_waitThreadNoChildrenCondition)

Sources/Testing/Expectations/ExpectationChecking+Macro.swift

@@ -139,7 +139,7 @@ private func _callBinaryOperator<T, U, R>(
   // nonescaping closure, but our use cases are safe (e.g. `true && false`) and
   // we cannot force one function or the other to be escaping. Use
   // withoutActuallyEscaping() to tell the compiler that what we're doing is
-  // okay. SEE: https://github.com/apple/swift-evolution/blob/main/proposals/0176-enforce-exclusive-access-to-memory.md#restrictions-on-recursive-uses-of-non-escaping-closures
+  // okay. SEE: https://github.com/swiftlang/swift-evolution/blob/main/proposals/0176-enforce-exclusive-access-to-memory.md#restrictions-on-recursive-uses-of-non-escaping-closures
   var rhsValue: U?
   let result: R = withoutActuallyEscaping(rhs) { rhs in
     op(lhs, {

Sources/Testing/Parameterization/TypeInfo.swift

@@ -184,27 +184,27 @@ extension TypeInfo {
 extension TypeInfo {
   /// Whether or not the described type is a Swift `enum` type.
   ///
-  /// Per the [Swift mangling ABI](https://github.com/apple/swift/blob/main/docs/ABI/Mangling.rst),
+  /// Per the [Swift mangling ABI](https://github.com/swiftlang/swift/blob/main/docs/ABI/Mangling.rst),
   /// enumeration types are mangled as `"O"`.
   ///
   /// - Bug: We use the internal Swift standard library function
   ///   `_mangledTypeName()` to derive this information. We should use supported
-  ///   API instead. ([swift-#69147](https://github.com/apple/swift/issues/69147))
+  ///   API instead. ([swift-#69147](https://github.com/swiftlang/swift/issues/69147))
   var isSwiftEnumeration: Bool {
     mangledName?.last == "O"
   }
 
   /// Whether or not the described type is imported from C, C++, or Objective-C.
   ///
-  /// Per the [Swift mangling ABI](https://github.com/apple/swift/blob/main/docs/ABI/Mangling.rst),
+  /// Per the [Swift mangling ABI](https://github.com/swiftlang/swift/blob/main/docs/ABI/Mangling.rst),
   /// types imported from C-family languages are placed in a single flat `__C`
   /// module. That module has a standardized mangling of `"So"`. The presence of
   /// those characters at the start of a type's mangled name indicates that it
   /// is an imported type.
   ///
   /// - Bug: We use the internal Swift standard library function
   ///   `_mangledTypeName()` to derive this information. We should use supported
-  ///   API instead. ([swift-#69146](https://github.com/apple/swift/issues/69146))
+  ///   API instead. ([swift-#69146](https://github.com/swiftlang/swift/issues/69146))
   var isImportedFromC: Bool {
     guard let mangledName, mangledName.count > 2 else {
       return false

Sources/Testing/SourceAttribution/Backtrace.swift

@@ -75,7 +75,7 @@ public struct Backtrace: Sendable {
         initializedCount = Int(RtlCaptureStackBackTrace(0, ULONG(addresses.count), addresses.baseAddress!, nil))
 #elseif os(WASI)
         // SEE: https://github.com/WebAssembly/WASI/issues/159
-        // SEE: https://github.com/apple/swift/pull/31693
+        // SEE: https://github.com/swiftlang/swift/pull/31693
         initializedCount = 0
 #else
 #warning("Platform-specific implementation missing: backtraces unavailable")
@@ -122,7 +122,7 @@ extension Backtrace {
     /// - Bug: On Windows, the weak reference to this object triggers a
     ///   crash. To avoid said crash, we'll keep a strong reference to the
     ///   object (abandoning memory until the process exits.)
-    ///   ([swift-#62985](https://github.com/apple/swift/issues/62985))
+    ///   ([swift-#62985](https://github.com/swiftlang/swift/issues/62985))
 #if os(Windows)
     var errorObject: (any AnyObject & Sendable)?
 #else