text
stringlengths
12
91.7k
metadata
dict
About migrations from Azure DevOps Cloud You can use to migrate repositories from Azure DevOps to ( or ). You can only use to migrate from Azure DevOps Cloud, not from Azure DevOps Server. If you currently use Azure DevOps Server and want to migrate to , you can migrate to Azure DevOps Cloud first. For more informat...
{ "source": "github-docs/migrations/ado/understand-migrations-from-azure-devops-to-github.md", "title": "Understand migrations from Azure DevOps to GitHub" }
[!NOTE] You can also use to perform your migration. See AUTOTITLE. Step 0: Get ready to use the GraphQL API Step 1: Get the ownerId for your migration destination Step 2: Identify where you're migrating from Your migration source is your ADO organization. createMigrationSource mutation mutation createMigrationSou...
{ "source": "github-docs/migrations/ado/use-graphql-to-migrate-repositories-from-azure-devops-to-github-enterprise-cloud.md", "title": "Use GraphQL to migrate repositories from Azure DevOps to GitHub Enterprise Cloud" }
What is ? () is a service for migrating repositories from to (). It is operated using a command line tool on . Migrations are "live" because users can continue using the source repository during most of the migration process. After the repository data is initially collected, webhooks check for changes to the reposit...
{ "source": "github-docs/migrations/elm/about-live-migrations.md", "title": "About live migrations from GitHub Enterprise Server to GHE.com" }
After you have run a migration with the elm CLI tool, there are some follow-up tasks to complete. Restore users' access Because and use different provisioning and authentication systems, organization membership is not carried over between platforms. You will need to add users to the organization before you can reatt...
{ "source": "github-docs/migrations/elm/complete-your-migration.md", "title": "Completing your live migration from GitHub Enterprise Server to GHE.com" }
elm migration commands Command Description ------ elm migration create Creates a new migration for a single source repository elm migration start --migration-id MIGRATION-ID Starts a migration elm migration status --migration-id MIGRATION-ID Shows the status, progress, cutover readiness, and timing of a migr...
{ "source": "github-docs/migrations/elm/elm-cli-reference.md", "title": "Enterprise Live Migrations CLI reference" }
[!TIP] As you follow this guide, you can refer to the AUTOTITLE for more detailed usage information. If you encounter errors, see AUTOTITLE. Prerequisites Make sure you're ready for your migration. See AUTOTITLE. 1. Create access tokens You must authenticate with a for both the source and destination of the migratio...
{ "source": "github-docs/migrations/elm/migrate-your-repository.md", "title": "Migrating your repository with Enterprise Live Migrations" }
Data that is migrated migrates almost all repository-level data. Organization-level resources, such as teams, projects, and organizations settings and webhooks, are excluded from the migration and must be configured manually on the target. The only organization-level action supported by is the creation of a target or...
{ "source": "github-docs/migrations/elm/migrated-data-reference.md", "title": "Migrated data for live migrations from GitHub Enterprise Server to GHE.com" }
Is our instance ready? is available in the latest patch releases for 3.17 and later. This documentation assumes you are using the following patch version or later. The instructions may not work on earlier versions. <!-- Update this list when we backport a change that meaningfully affects the instructions in the docs...
{ "source": "github-docs/migrations/elm/prepare-for-your-migration.md", "title": "Preparing for your live migration from GitHub Enterprise Server to GHE.com" }
If your migration encounters a problem, check the migration status with elm migration status --migration-id MIGRATION-ID and review the error information. Statuses and recommended actions Status Meaning Recommended action --------- Created The migration has been created but not yet started Run elm migration sta...
{ "source": "github-docs/migrations/elm/troubleshooting.md", "title": "Troubleshooting live migrations from GitHub Enterprise Server to GHE.com" }
About is a tool that quickly imports Git repositories from other hosting services to . To get started with , see AUTOTITLE. Capabilities and limitations of imports the source code and commit history of a repository. It does not import other associated data from the hosting service, such as issues and pull request...
{ "source": "github-docs/migrations/importing-source-code/using-github-importer/about-github-importer.md", "title": "About GitHub Importer" }
About repository imports with imports the source code and commit history of Git repositories hosted on external hosting services. For more information about the capabilities and limitations of , see AUTOTITLE. uses the email address in the commit header to link a commit to a user. To correctly attribute commits in ...
{ "source": "github-docs/migrations/importing-source-code/using-github-importer/importing-a-repository-with-github-importer.md", "title": "Importing a repository with GitHub Importer" }
If you want to import a Git repository to , and the repository is stored on a code hosting service that is publicly available on the internet, we recommend using . For more information, see AUTOTITLE. If your source code is not tracked by Git or is not publicly available, you can use the command line instead. You can u...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/about-source-code-imports-using-the-command-line.md", "title": "About source code imports using the command line" }
About importing source code Adding existing source code to If you have source code stored locally on your computer that is tracked by Git or not tracked by any version control system (VCS), you can add the code to by typing commands in a terminal. You can do this by typing Git commands directly. Alternatively, you c...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/adding-locally-hosted-code-to-github.md", "title": "Adding locally hosted code to GitHub" }
Prerequisites To follow these steps, you must use a macOS or Linux system and have the following tools installed: Mercurial Git () (see AUTOTITLE) Python, including the pip package manager Importing a Mercurial repository 1. To confirm that Mercurial is installed on your machine, run hg --version. The output s...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-mercurial-repository.md", "title": "Importing a Mercurial repository" }
Prerequisites To follow these steps, you must use a macOS or Linux system and have the following tools installed: Subversion Git, including git-svn () (see AUTOTITLE) Importing a Subversion repository 1. To confirm that git svn is available on your machine, run git svn --version. The output should be similar to...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-subversion-repository.md", "title": "Importing a Subversion repository" }
About imports from Team Foundation Version Control We recommend using Azure Repos to convert your Team Foundation Version Control (TFVC) repository to Git. However, Azure Repos only migrates up to 180 days of history. If you wish to retain more history, you can use git-tfs instead. Migrating with Azure Repos (recommen...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-a-team-foundation-version-control-repository.md", "title": "Importing a Team Foundation Version Control repository" }
Before you start, make sure you know: Your username The clone URL for the external repository, such as https://external-host.com/user/repo.git or git://external-host.com/user/repo.git (perhaps with a user@ in front of the external-host.com domain name) [!NOTE] For purposes of demonstration, we'll use: An externa...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-an-external-git-repository-using-the-command-line.md", "title": "Importing an external Git repository using the command line" }
Importing projects from Mercurial 1. Make a raw clone of the project using the command below, specifying the URL of the source project, and a path to a temporary repository: shell $ git-import-hg-raw HG-CLONE-URL/PATH/REPO-NAME.git Creates a new repository with one or more Git refs in "refs/import/" in the sp...
{ "source": "github-docs/migrations/importing-source-code/using-the-command-line-to-import-source-code/importing-from-other-version-control-systems-with-the-administrative-shell.md", "title": "Importing from other version control systems with the administrative shell" }
provides a variety of different tools to support these migrations. Different tools support different migration pathways and provide different levels of migration fidelity. Some tools, like migrate the current state of your code, all of the code's history, plus your settings and collaboration history, such as issues an...
{ "source": "github-docs/migrations/overview/about-githubs-migration-tooling.md", "title": "About GitHub's migration tooling" }
About locked repositories When you migrate repositories to or from products, your origin and destination repositories may be “locked” for migration. While a repository is locked, you cannot make any changes to the repository, such as pushing commits, creating issues, or commenting on pull requests. Whether your reposi...
{ "source": "github-docs/migrations/overview/about-locked-repositories.md", "title": "About locked repositories" }
What are mannequins? Each mannequin only has a display name, which comes from the display name in the source repository. Mannequins do not have organization membership or repository access. Mannequins always use the same avatar, a ghost octocat, and include a mannequin label following the display name. Reclaiming is op...
{ "source": "github-docs/migrations/overview/mannequins-and-user-activity.md", "title": "Mannequins and user activity" }
About migration paths to For some migration paths, we offer specialist tools that allow you to migrate source, history, and metadata. For others, you'll need to perform a simpler "source and history" or "source snapshot" migration. Some migration paths require tools that are only available with expert-led migrations....
{ "source": "github-docs/migrations/overview/migration-paths-to-github.md", "title": "Migration paths to GitHub" }
When would I migrate between platforms? You can use 's migration tools to move between platforms. For example: If you want to adopt , you can migrate your enterprise to . To use certain features on , such as or new billing models, you can migrate between enterprises on . To benefit from the simplified administrati...
{ "source": "github-docs/migrations/overview/migrations-within-github.md", "title": "About migrations between GitHub products" }
About migrations This guide will help you through planning and executing a successful migration. You’ll learn how to prepare for a migration, the tools that are available to move your data, and how to make your move a success. Migration terminology Before using this guide to plan your migration, learn these important ...
{ "source": "github-docs/migrations/overview/planning-your-migration-to-github.md", "title": "Planning your migration to GitHub" }
Term Definition ---- ---------- Code hosting platform The online tool that you use to host your source code repositories and to collaborate, such as , , Bitbucket Server, and GitLab.com. Version control system (VCS) The tool that you use to track and manage changes to your source code on the machine where you’re ...
{ "source": "github-docs/migrations/overview/planning-your-migration-to-github.md", "title": "Planning your migration to GitHub" }
Migration type Definition Requirements -------------- ---------- ------------ Source snapshot Migrate the current state of your code, as it is today, but don’t include any of the revision history. Possible for every origin and destination, even if your code isn’t currently tracked in a version control system (V...
{ "source": "github-docs/migrations/overview/planning-your-migration-to-github.md", "title": "Planning your migration to GitHub" }
Access to documentation Access to 's full range of tools Topics covered by support <ul<liExecution</li<liTroubleshooting</li</ul <ul<liPlanning</li<liExecution</li<liTroubleshooting</li</ul
{ "source": "github-docs/migrations/overview/planning-your-migration-to-github.md", "title": "Planning your migration to GitHub" }
Cost Free of charge Contact Expert Services for details To learn more about expert-led migrations, contact your account representative or Expert Services. Deciding what tools to use For more information, see AUTOTITLE. Designing your organization structure for the migration destination In , each repository belongs...
{ "source": "github-docs/migrations/overview/planning-your-migration-to-github.md", "title": "Planning your migration to GitHub" }
About programmatic import of repositories In the following guide, you can learn how to programmatically run "source and history" migrations of Git repositories to . Different options are available depending on where the repository is stored. To learn more about "source and history" and other types of migrations, see AU...
{ "source": "github-docs/migrations/overview/programmatically-importing-repositories.md", "title": "Programmatically importing repositories" }
Background When you import a repository with , an internal service pushes the repository's Git data to , batching refs together for performance. This introduces a possible case where evaluation of organization-level or enterprise-level rulesets against the pushed refs can time out, causing the repository migration as a...
{ "source": "github-docs/migrations/troubleshooting/setting-ruleset-bypasses-for-repository-migrations.md", "title": "Setting ruleset bypasses for repository migrations" }
About troubleshooting steps for If your migration fails or produces unexpected results, try the first steps for troubleshooting below, which commonly resolve a variety of issues. If these first steps do not resolve your issue, check for error messages in the logs for your migration. Then, locate the error message in t...
{ "source": "github-docs/migrations/troubleshooting/troubleshooting-your-migration-with-github-enterprise-importer.md", "title": "Troubleshooting your migration with GitHub Enterprise Importer" }
Types of migrations There are three types of migrations you can perform: A migration from a instance to another existing instance. You can migrate any number of repositories owned by any user or organization on the instance. Before performing a migration, you must have site administrator access to both instances. A...
{ "source": "github-docs/migrations/using-ghe-migrator/about-ghe-migrator.md", "title": "About ghe-migrator" }
Preparing the source instance 1. Verify that you are a site administrator on the source. The best way to do this is to verify that you can SSH into the instance. 1. on the source instance. Exporting the source repositories 1. To prepare a repository for export, use the ghe-migrator add command with the repository...
{ "source": "github-docs/migrations/using-ghe-migrator/exporting-migration-data-from-github-enterprise-server.md", "title": "Exporting migration data from GitHub Enterprise Server" }
Preparing the source organization on 1. Ensure that you have owner permissions on the source organization's repositories. 1. on . Exporting the organization's repositories To export repository data from , use the Migrations API. The Migrations API is currently in a preview period, which means that the endpoints and ...
{ "source": "github-docs/migrations/using-ghe-migrator/exporting-migration-data-from-githubcom.md", "title": "Exporting migration data from GitHub.com" }
Preparing the migrated data 1. Using the scp command, copy the migration archive generated from your source instance or organization to your target: shell scp -P 122 PATH-TO-MIGRATION-GUID.tar.gz admin@HOSTNAME:/home/admin/ 1. Ensure the migration archive has sufficient read permissions. shell chmod 644 /h...
{ "source": "github-docs/migrations/using-ghe-migrator/migrating-data-to-github-enterprise-server.md", "title": "Migrating data to GitHub Enterprise Server" }
About migration logs Each time you run a migration with , a migration log is created. You should check the migration log after every migration to review any migration warnings. The migration log lists the steps that were completed as part of the migration and includes additional information. Migration warnings, repres...
{ "source": "github-docs/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer.md", "title": "Accessing your migration logs for GitHub Enterprise Importer" }
For more information, see AUTOTITLE. Reclaiming mannequins You can reclaim mannequins with (recommended) or the browser. Reclaiming mannequins with the (recommended) Reclaiming mannequins in your browser [!NOTE] You cannot reclaim mannequins after you have transferred a repository to another organization. If yo...
{ "source": "github-docs/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer.md", "title": "Reclaiming mannequins for GitHub Enterprise Importer" }
For most customers, we recommend storing archives with . This is the simplest path and does not require any extra configuration. However, you may want to configure storage with an external provider if you have firewall requirements or need to retain archives after the migration is complete. Choosing where to stage arc...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/configure-storage.md", "title": "Configure blob storage" }
To allow someone other than an organization owner to run a migration or download migration logs, you can grant the migrator role to a user or team. To grant the migrator role using the CLI, you can use the . 1. On , create and record a that has the admin:org scope. 1. Use the gh gl2gh grant-migrator-role command, repl...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/grant-the-migrator-role.md", "title": "Granting the migrator role" }
Step 1: Install the is a collection of extensions for . If this is your first migration, you'll need to install and the . Step 2: Set environment variables Before you can use the to migrate to , you must create s that can access the source and destination, then set the s as environment variables. 1. Make sure you ...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/install-and-configure-github-enterprise-importer.md", "title": "Install and configure GitHub Enterprise Importer" }
To migrate repositories from GitLab to , you need sufficient access to the source (a project on GitLab) and the destination (an organization on ). After you complete the steps in this article, your access and permissions will be ready for your migration. Decide who will perform the migration If the person who will per...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/manage-access.md", "title": "Manage access for a migration from GitLab to GitHub" }
Prerequisites You must have completed all previous phases of this guide. The GitLab project must be enabled for exports. See Enable project export and Sidekiq configuration for imports in the GitLab documentation. For more information, see AUTOTITLE. Performing a trial run 1. Create a test organization for your tr...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/migrate-your-repositories.md", "title": "Migrate your repositories from GitLab to GitHub" }
Placeholder Value ----------- ----- GITLABSERVERURL The full URL of your GitLab instance, such as https://gitlab.com or https://gitlab.example.com. SOURCEGROUP The full path of the group or namespace that contains the project. For nested subgroups, use the full path, such as parent-group/subgroup. SOURCEPROJECT Th...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/migrate-your-repositories.md", "title": "Migrate your repositories from GitLab to GitHub" }
Placeholder Value ----------- ----- GITLABSERVERURL The full URL of your GitLab instance, such as https://gitlab.com or https://gitlab.example.com. DESTINATION The destination organization on . By default, the script includes every project the token can access. To scope the script, add --gitlab-group GROUP, or --gi...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/migrate-your-repositories.md", "title": "Migrate your repositories from GitLab to GitHub" }
Determine how much you have to migrate Figure out your timeline first, since it will largely shape your approach. The first step for determining your timeline is to get an inventory of what you need to migrate. Number of repositories (projects) Number of merge requests [!NOTE] Migration timing is largely based on the...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/plan-your-migration.md", "title": "Plan your migration from GitLab to GitHub" }
About migrations from GitLab You can use to migrate repositories from GitLab to ( or ). Migrations are performed with the , a cross-platform command-line wrapper around the migration APIs. For each repository, the : 1. Exports the GitLab project to a .tar.gz archive containing the Git repository plus project metadat...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/understand-migrations.md", "title": "Understand migrations from GitLab to GitHub" }
[!NOTE] You can also use to perform your migration. See AUTOTITLE. Step 0: Get ready to use the GraphQL API Step 1: Get the ownerId for your migration destination Step 2: Identify where you're migrating from Your migration source is your GitLab instance. createMigrationSource mutation mutation createMigrationSour...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrate-from-gitlab/use-graphql.md", "title": "Use GraphQL to migrate repositories from GitLab to GitHub Enterprise Cloud" }
About migrations between products With , you can migrate data from to , or migrate data from to another account on . If your migration source is an account on , you can migrate individual repositories between organizations, or migrate entire organizations between enterprises. If your migration source is , you can mi...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md", "title": "About migrations between GitHub products with {% data variables.product.prodname_importer_proper_name %}" }
Releases Different size limits per repository apply to the compressed archive, depending on your GHES version. Limit GHES <3.8.0 GHES 3.8.x-3.11.x GHES 3.12.x GHES 3.13.0+ ----- ----------- ----------------- ----------- ------------ Git source 2GiB 10GiB 20GiB 40GiB (public preview) Metadata 2GiB 10...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/about-migrations-between-github-products.md", "title": "About migrations between GitHub products with {% data variables.product.prodname_importer_proper_name %}" }
About required access for To run a migration, you need sufficient access to both the source and the destination for your migration. What are my source and destination? The source is the organization on or from which you want to migrate data. The destination can be: An organization account on or , if you're migrat...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md", "title": "Managing access for a migration between GitHub products" }
Task Organization owner Migrator ---- ------- ----- Running a migration Assigning the migrator role for repository migrations Destination organization or enterprise The following table lists which roles can perform which tasks. Task Enterprise owner Organization owner Migrator ---- ------------ ...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md", "title": "Managing access for a migration between GitHub products" }
Task Enterprise owner Organization owner Migrator ---- ------------------ -------- ----- Assigning the migrator role for repository migrations admin:org Running a repository migration (destination organization) repo, admin:org, workflow repo, read:org, workflow Downloading a migration log repo, admin...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/managing-access-for-a-migration-between-github-products.md", "title": "Managing access for a migration between GitHub products" }
About organization migrations with Migrations to include migrations between accounts on and, if you're adopting , migrations to your enterprise's subdomain of . Prerequisites For more information, see AUTOTITLE. For the source organization, you must be an organization owner or have the migrator role. For more in...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-organizations-from-githubcom-to-github-enterprise-cloud.md", "title": "Migrating organizations from GitHub.com to GitHub Enterprise Cloud" }
About repository migrations with If you choose to use the API, you'll need to write your own scripts or use an HTTP client like Insomnia. You can learn more about getting started with 's APIs in AUTOTITLE and AUTOTITLE. To migrate your repositories from to with the APIs, you will: 1. Create a for both the source an...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-github-enterprise-server-to-github-enterprise-cloud.md", "title": "Migrating repositories from GitHub Enterprise Server to GitHub Enterprise Cloud" }
About repository migrations with Migrations to include migrations between accounts on and, if you're adopting , migrations to your enterprise's subdomain of . Prerequisites For more information, see AUTOTITLE. In both the source and destination organization, you must be either an organization owner or be granted...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/migrating-repositories-from-githubcom-to-github-enterprise-cloud.md", "title": "Migrating repositories from GitHub.com to GitHub Enterprise Cloud" }
Overview With , you can migrate to . For more information, see AUTOTITLE. If you're migrating between products, such as from to , you can use this guide to plan and implement your migration and complete follow-up tasks. For a full list of supported migration paths, see AUTOTITLE. Planning your migration Do we want ...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-between-github-products/overview-of-a-migration-between-github-products.md", "title": "Overview of a migration between GitHub products" }
About migrations from Bitbucket Server You can use to migrate repositories from Bitbucket Server to ( or ). Migrations from Bitbucket Server are only supported for Bitbucket Server or Bitbucket Data Center version 5.14+ or higher. Data that is migrated We currently only support migrating the following repository dat...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/about-migrations-from-bitbucket-server-to-github-enterprise-cloud.md", "title": "About migrations from Bitbucket Server to GitHub Enterprise Cloud" }
About required access for To migrate a repository from Bitbucket Server to GitHub, you need sufficient access to both the source (your Bitbucket Server instance) and the destination (an organization on ). To have sufficient access, you'll need all of the following things. A required role in the destination organizati...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/managing-access-for-a-migration-from-bitbucket-server.md", "title": "Managing access for a migration from Bitbucket Server" }
About repository migrations with You can migrate individual repositories or all repositories from a BitBucket Server instance using . At this time, migrating from Bitbucket Server with the API is not supported. Prerequisites We strongly recommend that you perform a trial run of your migration and complete your prod...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/migrating-repositories-from-bitbucket-server-to-github-enterprise-cloud.md", "title": "Migrating repositories from Bitbucket Server to GitHub Enterprise Cloud" }
Overview With , you can migrate to on a repository-by-repository basis. For more information, see AUTOTITLE. If you're migrating from Bitbucket Server, you can use this guide to plan and implement your migration and complete follow-up tasks. Planning your migration How soon do we need to complete the migration? Do ...
{ "source": "github-docs/migrations/using-github-enterprise-importer/migrating-from-bitbucket-server-to-github-enterprise-cloud/overview-of-a-migration-from-bitbucket-server-to-github-enterprise-cloud.md", "title": "Overview of a migration from Bitbucket Server to GitHub Enterprise Cloud" }
About is a highly customizable migration tool designed to help you move your enterprise to . You can migrate on a repository-by-repository basis or, if your migration source is , on an organization-by-organization basis. allows you to customize your migration to meet your enterprise's unique needs with: A distinct ...
{ "source": "github-docs/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer.md", "title": "About GitHub Enterprise Importer" }
Introduction For Good First Issue curates social impact and civic tech open source projects that are looking for contributors and lists issues on those projects that are tagged with help wanted or good first issue. Open-source maintainers are always looking to get more people involved, but it can be challenging to beco...
{ "source": "github-docs/nonprofit/contributing-to-open-source-for-good/adding-an-open-source-project.md", "title": "Adding an open source project" }
Contribute to open source for good projects For Good First Issue curates social impact and civic tech open source projects that are looking for contributors and lists issues on those projects that are tagged with the help wanted or good first issue labels. Open source maintainers are always looking to get more people i...
{ "source": "github-docs/nonprofit/contributing-to-open-source-for-good/contributing-to-an-open-source-for-good-project.md", "title": "Contributing to an open source for good project" }
Introduction GitHub for Nonprofits offers 25% off GitHub Enterprise Cloud to access additional security, administrative, and customization options. As a registered nonprofit organization, you can apply for a GitHub for Nonprofits discount, including 25% off GitHub Enterprise Cloud. GitHub Enterprise Cloud allows admini...
{ "source": "github-docs/nonprofit/nonprofit-enterprise-plan/getting-started-with-discounted-github-enterprise-cloud.md", "title": "Getting started with discounted GitHub Enterprise Cloud" }
Introduction GitHub for Nonprofits offers free access to the GitHub Team plan to advance collaboration tools for individuals and organizations. As a registered nonprofit organization, you can apply for a GitHub for Nonprofits discount, including a free GitHub Team plan. Some features of GitHub Team include: Access to ...
{ "source": "github-docs/nonprofit/nonprofit-teams-plan/getting-started-with-the-github-team-plan-for-nonprofits.md", "title": "Getting started with the GitHub Team plan for nonprofits" }
Introduction Project Pods is a collaborative space where verified nonprofits can publish short-term, skills-based open source projects and small volunteer groups can team up to build meaningful solutions. The projects will then appear on For Good First Issue in the "For Teams" section. Project Pods are designed for tea...
{ "source": "github-docs/nonprofit/project-pods/creating-a-volunteering-project.md", "title": "Creating a Project Pod for volunteer groups" }
For nonprofits Who can submit a project? Any verified nonprofit that is part of the GitHub for Nonprofits program. Your organization must be a 501(c)(3) or equivalent nonprofit that is nongovernmental, nonacademic, noncommercial, and nonpolitical in nature. If you haven't joined yet, see AUTOTITLE to apply. What kind...
{ "source": "github-docs/nonprofit/project-pods/frequently-asked-questions.md", "title": "Frequently asked questions" }
Introduction GitHub for Nonprofits enables organizations to leverage technology to drive forward their missions and accelerate human progress. Verified nonprofits get exclusive access to a free GitHub Team plan or 25% off the GitHub Enterprise cloud plan. By hosting projects on GitHub, nonprofits can increase their vis...
{ "source": "github-docs/nonprofit/quickstart.md", "title": "Quickstart for GitHub for Nonprofits" }
If you cannot find your organization in the GitHub for Nonprofits portal, ensure that you are logged into GitHub for Nonprofits with an organization rather than an individual account. If you are running into trouble validating your organization as a nonprofit, please try the following steps. OAuth apps authorization R...
{ "source": "github-docs/nonprofit/troubleshooting/cannot-find-my-organization-on-github-for-nonprofits.md", "title": "Cannot find my organization on GitHub for Nonprofits" }
How do I convert my user account to an organization account? You will need an organization account to sign up for a GitHub for Nonprofits discount. Below is a guide to convert your account to an organization. Before you begin converting your account to an organization, set up a new personal GitHub account to manage the...
{ "source": "github-docs/nonprofit/troubleshooting/frequently-asked-questions.md", "title": "Frequently asked questions" }
About organizations For more information about account types, see AUTOTITLE. You can invite people to join your organization, then give these organization members a variety of roles that grant different levels of access to the organization and its data. For more information, see AUTOTITLE. If an organization exceeds 1...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/about-organizations.md", "title": "About organizations" }
Accessing your organization dashboard Finding your recent activity In the "Recent activity" section of your news feed, you can quickly find and follow up with recently updated issues and pull requests in your organization. Finding repositories in your organization In the left sidebar of your dashboard, you can access...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/about-your-organization-dashboard.md", "title": "About your organization dashboard" }
[!NOTE] The organization news feed is not available with . An organization's news feed shows other people's activity on repositories owned by that organization. You can use your organization's news feed to see when someone opens, closes, or merges an issue or pull request, creates or deletes a branch, creates a tag or ...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/about-your-organizations-news-feed.md", "title": "About your organization's news feed" }
[!TIP] Only organization owners and billing managers can see and change the billing information and the full set of account settings for an organization. Organization moderators only see moderation settings.
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/accessing-your-organizations-settings.md", "title": "Accessing your organization's settings" }
Assign multiple owners For more information, see AUTOTITLE. Use teams We recommend using teams to facilitate collaboration in your organization. For more information, see AUTOTITLE. We highly recommend managing team membership through your identity provider (IdP). For more information, see AUTOTITLE. We recommend kee...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/best-practices-for-organizations.md", "title": "Best practices for organizations" }
When you create a new organization from scratch, it doesn't have any repositories associated with it. For more information on adding repositories to your organization, see AUTOTITLE and AUTOTITLE. 1. Follow the prompts to create your organization. For more information about the plans available for your team, see AUTOTI...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/creating-a-new-organization-from-scratch.md", "title": "Creating a new organization from scratch" }
About your organization's profile page You can customize your organization's Overview page to show a README and pinned repositories dedicated to public users or members of the organization. Members of your organization who are signed into , can select a member or public view of the README and pinned repositories when t...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/customizing-your-organizations-profile.md", "title": "Customizing your organization's profile" }
About usage metrics About performance metrics Understanding metrics aggregation Viewing metrics for your organization
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/viewing-github-actions-metrics-for-your-organization.md", "title": "Viewing GitHub Actions metrics for your organization" }
Dependency insights can help you track, report, and act on your organization's open source usage. [!NOTE] To view organization dependency insights, your organization must use . Viewing organization dependency insights [!NOTE] Please make sure you have enabled the dependency graph. With dependency insights you can...
{ "source": "github-docs/organizations/collaborating-with-groups-in-organizations/viewing-insights-for-dependencies-in-your-organization.md", "title": "Viewing insights for dependencies in your organization" }
Two-factor authentication (2FA) provides basic authentication for organization members. By enabling 2FA, organization owners limit the likelihood that a member's account on could be compromised. For more information on 2FA, see AUTOTITLE. To add additional authentication measures, organization owners can also enable S...
{ "source": "github-docs/organizations/granting-access-to-your-organization-with-saml-single-sign-on/about-two-factor-authentication-and-saml-single-sign-on.md", "title": "About two-factor authentication and SAML single sign-on" }
To retain access for bots and service accounts, organization administrators can enable, but not enforce SAML single sign-on for their organization. If you need to enforce SAML single sign-on for your organization, you can create an external identity for the bot or service account with your identity provider (IdP). [!N...
{ "source": "github-docs/organizations/granting-access-to-your-organization-with-saml-single-sign-on/managing-bots-and-service-accounts-with-saml-single-sign-on.md", "title": "Managing bots and service accounts with SAML single sign-on" }
About SAML access to your organization When you enable SAML single sign-on for your organization, each organization member can link their external identity on your identity provider (IdP) to their existing account on . To access your organization's resources on , the member must have an active SAML session in their bro...
{ "source": "github-docs/organizations/granting-access-to-your-organization-with-saml-single-sign-on/viewing-and-managing-a-members-saml-access-to-your-organization.md", "title": "Viewing and managing a member's SAML access to your organization" }
About 's compliance reports You can access 's compliance reports in your organization settings. Accessing compliance reports for your organization 1. To the right of the report you want to access, click Download or View. Further reading AUTOTITLE
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/accessing-compliance-reports-for-your-organization.md", "title": "Accessing compliance reports for your organization" }
[!NOTE] This article contains the events available in the latest version of . Some of the events may not be available in previous versions. This article contains the events that may appear in your organization's audit log. For the events that can appear in a user account's security log or the audit log for an enter...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/audit-log-events-for-your-organization.md", "title": "Audit log events for your organization" }
[!NOTE] Displaying IP addresses in the audit log for an organization is in and subject to change. About display of IP addresses in the audit log By default, does not display the source IP address for events in your organization's audit log. If you enable this setting, the IP address will be displayed for new and e...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/displaying-ip-addresses-in-the-audit-log-for-your-organization.md", "title": "Displaying IP addresses in the audit log for your organization" }
About token data in the audit log for an organization Your organization's audit log contains an event for each action that a user or integration performs. If the action occurred outside of 's web UI, the event's data will show details about how the user or integration authenticated. Token data in audit log events Ide...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/identifying-audit-log-events-performed-by-an-access-token.md", "title": "Identifying audit log events performed by an access token" }
About allowed IP addresses By default, authorized users can access your organization's resources from any IP address. You can restrict access to your organization's private resources by configuring a list that allows or denies access from specific IP addresses. [!NOTE] Only organizations that use can use IP allow ...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization.md", "title": "Managing allowed IP addresses for your organization" }
About management of security and analysis settings can help you to secure the repositories in your organization. You can manage the security and analysis features for all existing or new repositories that members create in your organization. If you have a license for then you can also manage access to these features....
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-security-and-analysis-settings-for-your-organization.md", "title": "Managing security and analysis settings for your organization" }
About email restrictions When restricted email notifications are enabled in an organization, members can only use an email address associated with a verified or approved domain to receive email notifications about organization activity. For more information, see AUTOTITLE. [!NOTE] To restrict email notifications, you...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/restricting-email-notifications-for-your-organization.md", "title": "Restricting email notifications for your organization" }
Accessing the audit log [!NOTE] The audit log lists events triggered by activities that affect your organization within the last 180 days. Only owners can access an organization's audit log. Searching the audit log Search based on the action performed To search for specific events, use the action qualifier in your q...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/reviewing-the-audit-log-for-your-organization.md", "title": "Reviewing the audit log for your organization" }
About managing bots or service accounts with two-factor authentication (2FA) You should ensure that 2FA is enabled for unattended or shared access accounts in your organization, such as bots and service accounts, so that these accounts stay protected. Enabling 2FA for a bot or service account ensures that users must au...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/managing-bots-and-service-accounts-with-two-factor-authentication.md", "title": "Managing bots and service accounts with two-factor authentication" }
When requiring two-factor authentication in your organization, consider if you also want to enforce usage of only secure methods among your users (secure 2FA methods are passkeys, security keys, authenticator apps, and the GitHub mobile app). We recommend that you notify organization members, outside collaborators, and...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/preparing-to-require-two-factor-authentication-in-your-organization.md", "title": "Preparing to require two-factor authentication in your organization" }
About two-factor authentication for organizations You can require all members, outside collaborators, and billing managersmembers and outside collaborators in your organization to enable two-factor authentication on . For more information about two-factor authentication, see AUTOTITLE. You can also require two-factor ...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/requiring-two-factor-authentication-in-your-organization.md", "title": "Requiring two-factor authentication in your organization" }
[!NOTE] You can require that all members, including, owners, billing managers and and outside collaborators in your organization have two-factor authentication enabled, as well as enforcing that they have secure methods configured . For more information, see AUTOTITLE. 1. To view the two-factor authentication security...
{ "source": "github-docs/organizations/keeping-your-organization-secure/managing-two-factor-authentication-for-your-organization/viewing-whether-users-in-your-organization-have-2fa-enabled.md", "title": "Viewing whether users in your organization have 2FA enabled" }
About SSH certificate authorities An SSH certificate is a mechanism for one SSH key to sign another SSH key. If you use an SSH certificate authority (CA) to provide your organization members and outside collaborators with signed SSH certificates, you can add the CA to your enterprise account or organization to allow th...
{ "source": "github-docs/organizations/managing-git-access-to-your-organizations-repositories/about-ssh-certificate-authorities.md", "title": "About SSH certificate authorities" }
You can allow members to access your organization's repositories using SSH certificates you provide by adding an SSH CA to your organization. For more information, see AUTOTITLE. Adding an SSH certificate authority If you require SSH certificates for your enterprise, enterprise members should use a special URL for Gi...
{ "source": "github-docs/organizations/managing-git-access-to-your-organizations-repositories/managing-your-organizations-ssh-certificate-authorities.md", "title": "Managing your organization's SSH certificate authorities" }
Adding people to your organization If your organization requires members to use two-factor authentication, users must enable two-factor authentication before you can add them to the organization. Retrying or canceling expired invitations Invitations expire after 7 days. You can retry or cancel expired invitations, eit...
{ "source": "github-docs/organizations/managing-membership-in-your-organization/adding-people-to-your-organization.md", "title": "Adding people to your organization" }
About personal accounts Because you access an organization by logging in to a personal account, each of your team members needs to create their own personal account. After you have usernames for each person you'd like to add to your organization, you can add the users to teams. Organizations that use You can use SAML s...
{ "source": "github-docs/organizations/managing-membership-in-your-organization/can-i-create-accounts-for-people-in-my-organization.md", "title": "Can I create accounts for people in my organization?" }
1. Under "Organization permissions", click Invitations. 1. Next to the username of the person whose invitation you'd like to edit or cancel, click , then click Edit invitation, or click Cancel invitation. !Screenshot of the "Invitations" page. The "Edit invitation" and "Cancel invitation" buttons are highlighted wit...
{ "source": "github-docs/organizations/managing-membership-in-your-organization/canceling-or-editing-an-invitation-to-join-your-organization.md", "title": "Canceling or editing an invitation to join your organization" }
About export of membership information You can export aggregated information about your organization's members as a report. For example, you may want to perform an audit of your organization's current members. You can generate a file containing the report from 's web UI. The membership information report includes the f...
{ "source": "github-docs/organizations/managing-membership-in-your-organization/exporting-member-information-for-your-organization.md", "title": "Exporting member information for your organization" }