Add repository renaming process to request guidelines

Legal/requesting_new_repository.md

@@ -1,16 +1,16 @@
-# Requesting a New GitHub Repository
+# Requesting a New or Renaming an Existing GitHub Repository
 
 ## 1. Overview
 
 GitHub has strict rules regarding repository ownership and creation.
 
-Because all repositories within the ECMWF GitHub Enterprise are owned by ECMWF, individual users are **not permitted** to directly create repositories within those  ECMWF Github organisations.
+Because all repositories within the ECMWF GitHub Enterprise are owned by ECMWF, individual users are **not permitted** to directly create or rename repositories within those ECMWF GitHub organisations.
 
-Instead, all repository creations and transfers must go through a centralized request process to ensure compliance and management of the single namespace. This ensures ECMWF can properly manage naming conventions, visibility, access policies, compliance requirements, billing, and security settings for all assets under Github Enterprise.
+Instead, all repository creations, transfers, and renames must go through a centralized request process to ensure compliance and management of the single namespace. This ensures ECMWF can properly manage naming conventions, visibility, access policies, compliance requirements, billing, and security settings for all assets under GitHub Enterprise.
 
 ## 2. How to Request a Repository
 
-Whether you need to create a repository from scratch, transfer an existing repository from another GitHub owner, or migrate a repository from Bitbucket, you must submit a formal request.
+Whether you need to create a repository from scratch, transfer an existing repository from another GitHub owner, migrate a repository from Bitbucket, or **rename an existing repository**, you must submit a formal request.
 
 **Access the Request Form here:** [Form](https://forms.cloud.microsoft/pages/responsepage.aspx?id=xhG3IbeqNk2f-6wDV7wguiHmJMYpID5AlSzSoJeMPzBUNTBDQzM5RkJITDROWlBUTUNEQ1g4NlVNSS4u&route=shorturl)
 
@@ -25,12 +25,21 @@ Please have the following details ready before filling out the e-form:
    * *Note: See Section 4 for important rules regarding Public repositories.*
 * **Access Permissions:** A list of users or teams who need access, specifying their required permission levels (e.g., Admin, Write, Read).
 
+### Requesting a Repository Rename
+
+If you need to rename an existing repository, use the same request form above. Please have the following additional details ready:
+
+* **Current Repository Name:** The exact current name of the repository to be renamed.
+* **Proposed New Name:** The desired new name (this will be checked against availability and naming conventions).
+
+> **Important:** Renaming a repository changes its URL. While GitHub will automatically redirect traffic from the old URL to the new one, any hardcoded links, clone URLs, CI/CD configurations, or third-party integrations will need to be updated. Please inform your team and plan for this disruption before submitting your request.
+
 ## 3. Workflow and Approval Process
 
 Once your e-form is submitted, it follows a standard administrative workflow:
 
 1. **Review & Approval:** The Head of Development will review your request to ensure it aligns with ECMWF's software strategy and naming conventions. Your repository name will be checked for clarity and relevance to its intended purpose. You may be contacted for additional information or clarification during this stage, including a discussion on the name and scope of the repository.
-2. **Creation & Configuration:** If approved, **User Services** will manually create or transfer the repository and apply the requested access permissions. You maybe contacted to clarify some technical details of the repository setup, or as part of the transfer process if applicable.
+2. **Creation, Rename & Configuration:** If approved, **User Services** will manually create, rename, or transfer the repository and apply the requested access permissions. You may be contacted to clarify some technical details of the repository setup, or as part of the transfer process if applicable.
 3. **Notification:** You will receive a notification once your repository is set up and ready to use. Please check that your permissions are correctly applied and that the repository is configured as requested.
 4. **Check Branch Protection Rules:** If applicable, ensure that any necessary branch protection rules are set up to maintain code quality and security standards (e.g., ensuring the main branches are protected, requiring pull request reviews, status checks, etc).
 
@@ -41,4 +50,4 @@ Requesting a **Public** repository (or changing an existing repository's visibil
 If your repository requires public visibility, you must complete the official open-sourcing approval procedure.
 Your repository will be first made Private and only made Public once the open-sourcing process is complete and approved.
 
-Please review and follow the guidelines documented here: [Open Sourcing Software Procedure](https://github.com/ecmwf/codex/blob/main/Legal/open_sourcing_software.md)
+Please review and follow the guidelines documented here: [Open Sourcing Software Procedure](https://github.com/ecmwf/codex/blob/main/Legal/open_sourcing_software.md)