Adjust links to point to GitHub project

Author: pratlucas

arm-software/embedded/CMakeLists.txt

@@ -186,7 +186,7 @@ if(LLVM_TOOLCHAIN_LIBRARY_OVERLAY_INSTALL)
   endif()
 endif()
 
-set(BUG_REPORT_URL "https://gitlab.arm.com/toolchains/arm-toolchain/-/issues" CACHE STRING "")
+set(BUG_REPORT_URL "https://github.com/arm/arm-toolchain/issues" CACHE STRING "")
 set(LLVM_DISTRIBUTION_COMPONENTS
     clang-resource-headers
     clang
@@ -374,7 +374,7 @@ project(
     ArmToolchainForEmbedded
     VERSION ${LLVM_VERSION_MAJOR}.${LLVM_VERSION_MINOR}.${LLVM_VERSION_PATCH}
     DESCRIPTION "Arm Toolchain for Embedded"
-    HOMEPAGE_URL "https://gitlab.arm.com/toolchains/arm-toolchain"
+    HOMEPAGE_URL "https://github.com/arm/arm-toolchain"
 )
 
 # Set package name for shorter archive file name

arm-software/embedded/README.md

@@ -76,13 +76,13 @@ The Windows version is built on Windows Server 2019 and lightly tested on Window
 
 Building on macOS is functional for x86_64 and Apple Silicon.
 
-[Binary packages](https://gitlab.arm.com/toolchains/arm-toolchain/-/releases)
+[Binary packages](https://github.com/arm/arm-toolchain/-/releases)
 are provided for major LLVM releases for Linux and Windows.
 
 ## Getting started
 
 Download a release of the toolchain for your platform from [Github
-releases](https://gitlab.arm.com/toolchains/arm-toolchain/-/releases)
+releases](https://github.com/arm/arm-toolchain/-/releases)
 and extract the archive into an arbitrary directory.
 
 ### Pre-requisite for using toolchain on Windows
@@ -201,7 +201,7 @@ guide for detailed instructions.
 
 ## Providing feedback and reporting issues
 
-Please raise an issue via [Github issues](https://gitlab.arm.com/toolchains/arm-toolchain/-/issues).
+Please raise an issue via [Github issues](https://github.com/arm/arm-toolchain/issues).
 
 ## Contributions and Pull Requests
 

arm-software/embedded/cmake/VERSION.txt.in

@@ -1,5 +1,5 @@
 Arm Toolchain for Embedded ${armtoolchain_VERSION}
 
 Sources:
-* arm-toolchain: https://gitlab.arm.com/toolchains/arm-toolchain (commit ${armtoolchain_COMMIT})
+* arm-toolchain: https://github.com/arm/arm-toolchain (commit ${armtoolchain_COMMIT})
 * Picolibc: https://github.com/picolibc/picolibc.git (commit ${picolibc_COMMIT})

arm-software/embedded/docs/building-from-source.md

@@ -162,7 +162,7 @@ The same build directory can be used for both native and MinGW toolchains.
 
 ## Divergences from upstream
 
-See [patches](https://gitlab.arm.com/toolchains/arm-toolchain/-/blob/arm-software/embedded/patches)
+See [patches](https://github.com/arm/arm-toolchain/-/blob/arm-software/embedded/patches)
 directory for the current set of differences from upstream.
 
 The patches for llvm-project are split between two folders, llvm-project and

arm-software/embedded/docs/contributing.md

@@ -26,7 +26,7 @@ For guidance on how to contribute to the upstream projects see:
 ### Report an issue
 
 Please create a Github issue in the *Arm Toolchain for Embedded* project
-[Issues](https://gitlab.arm.com/toolchains/arm-toolchain/-/issues)
+[Issues](https://github.com/arm/arm-toolchain/issues)
 list and label is as a `bug`.
 
 ### Submit a fix
@@ -38,7 +38,7 @@ _How to submit a change_ section below.
 
 For a bigger change, please create an issue in the
 *Arm Toolchain for Embedded* project
-[Issues](https://gitlab.arm.com/toolchains/arm-toolchain/-/issues)
+[Issues](https://github.com/arm/arm-toolchain/issues)
 list and label is as an `rfc` (Request for Comments) to initiate the discussion
 first, before submitting the change itself.
 
@@ -48,7 +48,7 @@ the purpose of the change and the key design options, proposed decisions.
 ## How to submit a change
 
 Contributions are accepted under the
-[Apache License 2.0](https://gitlab.arm.com/toolchains/arm-toolchain/-/blob/arm-software/embedded/LICENSE.txt).
+[Apache License 2.0](https://github.com/arm/arm-toolchain/-/blob/arm-software/embedded/LICENSE.txt).
 Only submit contributions where you have authored all of the code.
 
 ### Pull request

arm-software/embedded/docs/migrating.md

@@ -20,7 +20,7 @@ particularly C and C++ standards compliance, during build time.
 Arm Toolchain for Embedded provides support for multiple sanitizers
 and memory safety features to also catch typical issues at runtime during testing,
 see the [Clang documentation](https://clang.llvm.org/docs/index.html)
-and [samples](https://gitlab.arm.com/toolchains/arm-toolchain/-/blob/arm-software/embedded/samples/src).
+and [samples](https://github.com/arm/arm-toolchain/-/blob/arm-software/embedded/samples/src).
 
 Arm Toolchain for Embedded provides superior performance when targeting the
 Armv8-M or later architecture, including the
@@ -83,7 +83,7 @@ For example, GNU and LLVM compilers differ in:
 ## Multilib support
 
 LLVM toolchain for Arm provides multilib support similar to the GNU toolchain,
-see _Using the toolchain_ section in the [README](https://gitlab.arm.com/toolchains/arm-toolchain/-/blob/arm-software/embedded/README.md#using-the-toolchain),
+see _Using the toolchain_ section in the [README](https://github.com/arm/arm-toolchain/-/blob/arm-software/embedded/README.md#using-the-toolchain),
 however uses different command line options to control selection of semihosting.
 
 |Use case|GNU options|LLVM options|
@@ -121,5 +121,5 @@ section and referenced by the `__interrupt_vector` symbol.
 See [Picolibc and Operating Systems](https://github.com/picolibc/picolibc/blob/main/doc/os.md)
 for the details on redirecting `stdin`, `stdout` and `stderr`.
 
-The `baremetal-uart` [sample](https://gitlab.arm.com/toolchains/arm-toolchain/-/blob/arm-software/embedded/samples/src/baremetal-uart)
+The `baremetal-uart` [sample](https://github.com/arm/arm-toolchain/-/blob/arm-software/embedded/samples/src/baremetal-uart)
 provides a basic code example for redirecting `stdout`.