Add repository renaming process to request guidelines

[bkasic]

Updated the document to include repository renaming process and its implications.

Description

Contributor Declaration

By opening this pull request, I affirm the following:

• All authors agree to the Contributor License Agreement.
• The code follows the project's coding standards.
• I have performed self-review and added comments where needed.
• I have added or updated tests to verify that my changes are effective and functional.
• I have run all existing tests and confirmed they pass.

[Copilot]

Pull request overview

Updates the repository request guidelines to explicitly cover repository renames and highlight operational implications (URL changes and downstream updates) within the ECMWF GitHub Enterprise process.

Changes:

• Expands the scope of the guidelines to include repository renaming alongside creation and transfers.
• Adds a dedicated “Requesting a Repository Rename” subsection with required details and an impact warning.
• Updates the workflow section to reflect rename handling by User Services.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The H1 heading reads awkwardly and includes a trailing space. Consider rephrasing to something like “Requesting a New or Renaming an Existing GitHub Repository” (and remove the trailing whitespace) for correct grammar/capitalization.

Suggested change

	# Requesting a New or Renaming existing GitHub Repository
	# Requesting a New or Renaming an Existing GitHub Repository

[Copilot]

Use the correct GitHub capitalization (“GitHub”, not “Github”) and remove the double space in “those ECMWF …” to keep wording consistent and avoid typos in the docs.

[Copilot]

This paragraph also uses “Github Enterprise”; please capitalize it as “GitHub Enterprise” for consistency with GitHub branding used elsewhere in the document.

Suggested change

	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.
	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.

[Copilot]

Missing comma after “rename an existing repository” makes the sentence hard to parse. Add a comma before “you must submit a formal request.”

Suggested change

	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.
	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.

[Copilot]

Grammar: “You maybe contacted” should be “You may be contacted”. Also consider adding a comma in “create, rename, or transfer” for readability.

Suggested change

	2. **Creation, Rename & Configuration:** If approved, **User Services** will manually create, rename 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.