Skip to content

Add repository renaming process to request guidelines #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tlmquintino merged 3 commits into from
Apr 15, 2026
Merged

Add repository renaming process to request guidelines #57

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d7724d1
Add repository renaming process to request guidelines
bkasic Apr 14, 2026
8000622
Merge branch 'main' into bkasic-patch-1
tlmquintino Apr 15, 2026
1ba3002
Address Copilot review: fix heading grammar, GitHub capitalisation, d…
tlmquintino Apr 15, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 15 additions & 6 deletions Legal/requesting_new_repository.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,16 +1,16 @@
# Requesting a New GitHub Repository
# Requesting a New or Renaming existing GitHub Repository
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uses AI. Check for mistakes.

## 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.
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uses AI. Check for mistakes.

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

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uses AI. Check for mistakes.

## 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.
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uses AI. Check for mistakes.

**Access the Request Form here:** [Form](https://forms.cloud.microsoft/pages/responsepage.aspx?id=xhG3IbeqNk2f-6wDV7wguiHmJMYpID5AlSzSoJeMPzBUNTBDQzM5RkJITDROWlBUTUNEQ1g4NlVNSS4u&route=shorturl)

Expand All @@ -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 maybe contacted to clarify some technical details of the repository setup, or as part of the transfer process if applicable.
Copy link

Copilot AI Apr 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copilot uses AI. Check for mistakes.
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).

Expand All @@ -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)