Repo sync

content/admin/data-residency/getting-started-with-data-residency-for-github-enterprise-cloud.md

@@ -115,7 +115,7 @@ To migrate existing data to your new enterprise on {% data variables.enterprise.
 
 Optionally, you can migrate data to {% data variables.enterprise.data_residency_site %} during your trial. However, migrated organizations will count towards the limit of three new organizations during the trial.
 
-* If you're migrating from {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_ghe_server %}, Azure DevOps, or Bitbucket Server, you can migrate source code history and metadata with {% data variables.product.prodname_importer_proper_name %}. See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer).
+* If you're migrating from {% data variables.product.prodname_dotcom_the_website %}, {% data variables.product.prodname_ghe_server %}, Azure DevOps, Bitbucket Server, or GitLab, you can migrate source code history and metadata with {% data variables.product.prodname_importer_proper_name %}. See [AUTOTITLE](/migrations/using-github-enterprise-importer/understanding-github-enterprise-importer/about-github-enterprise-importer).
 * For migrations from {% data variables.product.prodname_ghe_server %} 3.17 and later, you can use {% data variables.product.prodname_elm %}. This offers less downtime and better support for complex monorepos. See [AUTOTITLE](/migrations/elm/about-live-migrations).
 * If you're migrating from a different platform, see [AUTOTITLE](/migrations/overview/migration-paths-to-github#migrations-to-ghecom).
 

content/code-security/concepts/vulnerability-reporting-and-management/github-advisory-database.md

@@ -41,17 +41,17 @@ Both of these advisory types are public information about open source packages.
 
 Generally, we name our supported ecosystems after the software programming language's associated package registry. We review advisories if they are for a vulnerability in a package that comes from a supported registry.
 
-* Composer (registry: https://packagist.org/)
-* Erlang (registry: https://hex.pm/)
-* Go (registry: https://pkg.go.dev/)
-* GitHub Actions (https://github.com/marketplace?type=actions/)
-* Maven (registry: https://repo.maven.apache.org/maven2)
-* Npm (registry: https://www.npmjs.com/)
-* NuGet (registry: https://www.nuget.org/)
-* Pip (registry: https://pypi.org/)
-* Pub (registry: https://pub.dev/packages/registry)
-* RubyGems (registry: https://rubygems.org/)
-* Rust (registry: https://crates.io/)
+* Composer (registry: [https://packagist.org/](https://packagist.org/))
+* Erlang (registry: [https://hex.pm/](https://hex.pm/))
+* Go (registry: [https://pkg.go.dev/](https://pkg.go.dev/))
+* GitHub Actions ([https://github.com/marketplace?type=actions](https://github.com/marketplace?type=actions))
+* Maven (registry: [https://repo.maven.apache.org/maven2](https://repo.maven.apache.org/maven2))
+* Npm (registry: [https://www.npmjs.com/](https://www.npmjs.com/))
+* NuGet (registry: [https://www.nuget.org/](https://www.nuget.org/))
+* Pip (registry: [https://pypi.org/](https://pypi.org/))
+* Pub (registry: [https://pub.dev/packages/registry](https://pub.dev/packages/registry))
+* RubyGems (registry: [https://rubygems.org/](https://rubygems.org/))
+* Rust (registry: [https://crates.io/](https://crates.io/))
 * Swift (registry: N/A)
 
 If you have a suggestion for a new ecosystem we should support, please open an [issue](https://github.com/github/advisory-database/issues) for discussion.
@@ -68,7 +68,13 @@ If you enable {% data variables.product.prodname_dependabot_alerts %} for your r
 
 {% data reusables.advisory-database.malware-overview %}
 
-{% data variables.product.prodname_dependabot %} doesn't generate alerts when malware is detected as most of the vulnerabilities cannot be resolved by downstream users. You can view malware advisories by searching for `type:malware` in the {% data variables.product.prodname_advisory_database %}.
+{% ifversion dependabot-malware-alerts-multi-ecosystem %}
+
+When malware alerts are enabled, {% data variables.product.prodname_dependabot %} generates an alert when malware is detected. For more information, see [AUTOTITLE](/code-security/how-tos/secure-your-supply-chain/secure-your-dependencies/configure-malware-alerts).
+
+{% endif %}
+
+You can view malware advisories by searching for `type:malware` in the {% data variables.product.prodname_advisory_database %}.
 
 Our malware advisories are mostly about substitution attacks. During this type of attack, an attacker publishes a package to the public registry with the same name as a dependency that users rely on from a third party or private registry, with the hope that the malicious version is consumed. {% data variables.product.prodname_dependabot %} doesn't look at project configurations to determine if the packages are coming from a private registry, so we can't determine whether you're using the malicious version or a non-malicious version that has the same name. Users who have their dependencies appropriately scoped should not be affected by malware.
 
@@ -100,6 +106,7 @@ The {% data variables.product.prodname_advisory_database %} supports both CVSS v
 Each security advisory contains information about the vulnerability or malware, which may include the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the [National Vulnerability Database](https://nvd.nist.gov/) from the National Institute of Standards and Technology.
 
 The severity level is one of four possible levels defined in the [Common Vulnerability Scoring System (CVSS), Section 5](https://www.first.org/cvss/specification-document).
+
 * Low
 * Medium/Moderate
 * High
@@ -111,7 +118,7 @@ The {% data variables.product.prodname_advisory_database %} uses the CVSS levels
 
 ### EPSS scores
 
-The Exploit Prediction Scoring System, or EPSS, is a system devised by the global Forum of Incident Response and Security Teams (FIRST) for quantifying the likelihood of vulnerability exploit. The model produces a probability score between 0 and 1 (0 and 100%), where the higher the score, the greater the probability that a vulnerability will be exploited. For more information about FIRST, see https://www.first.org/.
+The Exploit Prediction Scoring System, or EPSS, is a system devised by the global Forum of Incident Response and Security Teams (FIRST) for quantifying the likelihood of vulnerability exploit. The model produces a probability score between 0 and 1 (0 and 100%), where the higher the score, the greater the probability that a vulnerability will be exploited. For more information about FIRST, see [https://www.first.org/](https://www.first.org/).
 
 The {% data variables.product.prodname_advisory_database %} includes EPSS scores from FIRST for advisories containing CVEs with corresponding EPSS data. {% data variables.product.company_short %} also displays the EPSS score percentile, which is the proportion of all scored vulnerabilities with the same or a lower EPSS score.
 

content/code-security/reference/supply-chain-security/dependabot-options-reference.md

@@ -563,7 +563,7 @@ Package manager | YAML value      | Supported versions |
 | {% ifversion dependabot-bazel-support %} |
 | Bazel         | `bazel`          | v7, v8, v9               |
 | {% endif %} |
-| Bun | `bun`         | >=v1.2.5              |
+| Bun | `bun`         | >=v1.1.39              |
 | Bundler | `bundler` | v2 |
 | Cargo       | `cargo`          | v1               |
 | Composer       | `composer`       | v2         |
@@ -593,14 +593,14 @@ Package manager | YAML value      | Supported versions |
 | {% ifversion dependabot-nix-support %} |
 | Nix flakes | `nix`            | Not applicable   |
 | {% endif %} |
-| npm            | `npm`            |  v7, v8, v9, v10   |
+| npm            | `npm`            |  v7, v8, v9, v10, v11   |
 | NuGet          | `nuget`          | <=6.12.0 |
 | {% ifversion dependabot-opentofu-support %} |
 | OpenTofu     | `opentofu`       | Not applicable     |
 | {% endif %} |
-| pip         | `pip`            | 24.2             |
+| pip         | `pip`            | 26.1.1             |
 | pip-compile | `pip`            | 7.5.3            |
-| pipenv      | `pip`            | <= 2024.4.1      |
+| pipenv      | `pip`            | 2024.4.1      |
 | pnpm   | `npm`            | v7, v8, v9, v10   |
 | poetry      | `pip`    | v2    |
 | {% ifversion dependabot-pre-commit-support %} |
@@ -614,7 +614,7 @@ Package manager | YAML value      | Supported versions |
 | sbt          | `sbt`            | Not applicable   |
 | {% endif %} |
 | Swift   | `swift`      | v5  |
-| Terraform    | `terraform`      | >= 0.13, <= 1.10.x  |
+| Terraform    | `terraform`      | >= 0.13, <= 1.15.x  |
 | uv           | `uv`             | v0 |
 | {% ifversion dependabot-vcpkg-support %} |
 | vcpkg       | `vcpkg`          | Not applicable   |

content/migrations/ado/follow-up-tasks.md

@@ -12,48 +12,7 @@ redirect_from:
   - /migrations/ado/phase-6-follow-up-tasks
 ---
 
-## Checking the migration status
-
-First, check whether your migration succeeded or failed.
-
-The way you check the status of your migration depends on how you ran the migration.
-
-* If you ran the migration using the {% data variables.product.prodname_cli %}, by default, the process will display whether the migration succeeded or failed once the migration is complete. If the migration failed, you will see the reason for failure.
-
-  ```text
-  Migration completed (ID: RM_123)! State: SUCCEEDED
-  ```
-
-* If you ran the migration using the {% data variables.product.prodname_cli %} with the optional `--queue-only` argument, the process will exit immediately after queueing the migration, and will not tell you if the migration succeeded or failed. You can check a migration's status using the `wait-for-migration` command, or by reviewing the migration log.
-
-## Reviewing the migration log
-
-You should review the migration log for each migrated repository. People with read access to a repository can access the migration log for the repository on {% data variables.product.prodname_dotcom %}.
-
-1. Navigate to the migrated repository in your destination organization.
-{% data reusables.repositories.sidebar-issues %}
-1. Click the issue with the title "Migration Log."
-
-For more information, see [AUTOTITLE](/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/accessing-your-migration-logs-for-github-enterprise-importer).
-
-## Setting repository visibility
-
-{% data reusables.enterprise-migration-tool.setting-repository-visibility %}
-
-   For example, replace YOUR_ORG with your organization name, and the command below will set all of the organization's repositories to internal visibility.
-
-   ```bash copy
-   export ORG=YOUR_ORG
-   gh repo list "$ORG" --limit 100000 --json name -q '.[].name' | xargs -I{} gh repo edit "$ORG/{}" --visibility internal
-   ```
-
-## Reclaiming mannequins
-
-{% data reusables.enterprise-migration-tool.reclaiming-mannequins %}
-
-## Configuring IP allow lists
-
-If you added the IP ranges for {% data variables.product.prodname_importer_proper_name %} to the IP allow list for your destination organization, you can remove those entries. {% data reusables.enterprise-migration-tool.reenable-idp-ip-restrictions %}
+{% data reusables.enterprise-migration-tool.follow-up-tasks-common %}
 
 ## Configure Azure Pipelines and Azure Boards
 

content/migrations/ado/understand-migrations-from-azure-devops-to-github.md

@@ -46,21 +46,4 @@ If you want to migrate Azure Pipelines to {% data variables.product.prodname_act
 * Attachments on pull requests
 * Branch policies for the repository (user-scoped branch policies and cross-repo branch policies are not included)
 
-## Limitations on migrated data
-
-There are limits to what {% data variables.product.prodname_importer_proper_name %} can migrate. Some are due to limitations of {% data variables.product.prodname_dotcom %}, while others are limitations of {% data variables.product.prodname_importer_proper_name %} itself.
-
-### Limitations of {% data variables.product.prodname_dotcom %}
-
-* **2 GiB size limit for a single Git commit:** No single commit in your Git repository can be larger than 2 GiB. If any of your commits are larger than 2 GiB, you will need to split the commit into smaller commits that are each 2 GiB or smaller.
-* **255 byte limit for Git references:** No single Git reference, commonly known as a "ref", can have a name larger than 255 bytes. Usually, this means that your references cannot be more than 255 characters long, but any non-ASCII characters, such as emojis, may consume more than one byte. If any of your Git references are too large, we'll return a clear error message.
-* **100 MiB file size limit:** After you complete your migration, no single file in your Git repository can be larger than 100 MiB. During repository migration this limit is increased to 400 MiB. Consider using {% data variables.large_files.product_name_short %} to store large files.
-
-### Limitations of {% data variables.product.prodname_importer_proper_name %}
-
-* {% data reusables.enterprise-migration-tool.git-repo-size-limit %}
-* **400 MiB file size limit:** When migrating a repository with {% data variables.product.prodname_importer_proper_name %}, no single file in your Git repository can be larger than 400 MiB. Consider using {% data variables.large_files.product_name_short %} for storing large files.
-* **{% data variables.large_files.product_name_short %} objects not migrated:** The {% data variables.product.prodname_importer_secondary_name %} can migrate repositories that use {% data variables.large_files.product_name_short %}, but the LFS objects themselves will not be migrated. They can be pushed to your migration destination as a follow-up task after the migration is complete.
-* **Delayed code search functionality:** Re-indexing the search index can take a few hours after a repository is migrated, and code searches may return unexpected results until re-indexing is complete.
-* **Rulesets configured for your organization can cause migrations to fail:** For example, if you configured a rule that requires email addresses for commit authors to end with `@monalisa.cat`, and the repository you're migrating contains commits that don't comply with this rule, your migration will fail.
-* **Mannequin content might not be searchable:** Mannequins are placeholder users to which imported content (such as issues, pull requests, comments, etc.) is associated. When you search for content associated with a mannequin, such as assigned issues, the issues may not be found. Once a mannequin is reclaimed, the content should be found via the new owner.
+{% data reusables.enterprise-migration-tool.migration-data-limitations %}

content/migrations/overview/migration-paths-to-github.md

@@ -101,10 +101,7 @@ Migrations from {% data variables.product.prodname_dotcom_the_website %} include
 
 * **Scope:** Source, history, and metadata
 * **Tooling:** {% data variables.product.prodname_importer_proper_name %}
-* **More information:** [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
-* **Caveats:**
-  * If you want to migrate GitLab repositories to GitHub using {% data variables.product.prodname_importer_proper_name %}, please contact our {% data variables.product.prodname_expert_services %} team.
-  * {% data reusables.migrations.migration-instructions-for-any-git-repository-to-githubcom %}
+* **More information:** [AUTOTITLE]({% ifversion ghes %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer/migrate-from-gitlab)
 
 ### Any Git repository to {% data variables.product.prodname_dotcom_the_website %}
 
@@ -233,10 +230,8 @@ Follow a link below to review the scope and tooling for your migration to {% dat
 ### GitLab to {% data variables.enterprise.data_residency_site %}
 
 * **Scope:** Source, history, and metadata
-* **Tooling:** Contact {% data variables.product.prodname_expert_services %}
-* **More information:** [{% data variables.product.prodname_expert_services %}](https://github.com/services/) website
-* **Caveats:**
-  * {% data reusables.migrations.migration-instructions-for-any-git-repository-to-ghecom %}
+* **Tooling:** {% data variables.product.prodname_importer_proper_name %}
+* **More information:** [AUTOTITLE]({% ifversion ghes %}/free-pro-team@latest{% endif %}/migrations/using-github-enterprise-importer/migrate-from-gitlab)
 
 ### Any Git repository to {% data variables.enterprise.data_residency_site %}
 

content/migrations/using-github-enterprise-importer/completing-your-migration-with-github-enterprise-importer/reclaiming-mannequins-for-github-enterprise-importer.md

@@ -38,6 +38,9 @@ The exact command you need to use depends on which extension of the {% data vari
 * [Reclaiming mannequins with the {% data variables.product.prodname_gei_cli_short %}](#reclaiming-mannequins-with-the-gei-extension)
 * [Reclaiming mannequins with the {% data variables.product.prodname_ado2gh_cli_short %}](#reclaiming-mannequins-with-the-ado2gh-extension)
 * [Reclaiming mannequins with the {% data variables.product.prodname_bbs2gh_cli_short %}](#reclaiming-mannequins-with-the-bbs2gh-extension)
+{%- ifversion fpt or ghec %}
+* [Reclaiming mannequins with the {% data variables.product.prodname_gl2gh_cli_short %}](#reclaiming-mannequins-with-the-gl2gh-extension)
+{%- endif %}
 
 #### Reclaiming mannequins with the {% data variables.product.prodname_gei_cli_short %}
 
@@ -141,6 +144,44 @@ If your migration source is Bitbucket Server, you can reclaim mannequins with th
 
 {% data reusables.enterprise-migration-tool.mannequin-reclaim-must-accept %}
 
+{% ifversion fpt or ghec %}
+
+#### Reclaiming mannequins with the {% data variables.product.prodname_gl2gh_cli_short %}
+
+If your migration source is GitLab, you can reclaim mannequins with the {% data variables.product.prodname_gl2gh_cli %}.
+
+* If you don't already have a `GH_PAT` environment variable set for a {% data variables.product.pat_generic %} with access to the destination organization, add `--github-pat TOKEN` to each command below, replacing `TOKEN` with the {% data variables.product.pat_generic %}. For {% data variables.product.pat_generic %} requirements, see [AUTOTITLE](/migrations/using-github-enterprise-importer/migrate-from-gitlab/manage-access).
+* {% data reusables.enterprise-migration-tool.add-target-api-url %}
+
+{% data reusables.enterprise-migration-tool.create-csv-mannequins %}
+
+   * To generate a CSV file with a list of mannequins for an organization, use the `gh gl2gh generate-mannequin-csv` command, replacing DESTINATION with the destination organization and FILENAME with a file name for the resulting CSV file.
+
+     {% data reusables.enterprise-migration-tool.include-reclaimed %}
+
+     ```shell copy
+     gh gl2gh generate-mannequin-csv --github-org DESTINATION --output FILENAME.csv
+     ```
+
+   {% data reusables.enterprise-migration-tool.edit-csv %}
+1. To reclaim mannequins, use the `gh gl2gh reclaim-mannequin` command.
+
+    {% data reusables.enterprise-migration-tool.reclaim-bulk-csv %}
+
+      ```shell copy
+      gh gl2gh reclaim-mannequin --github-org DESTINATION --csv FILENAME.csv
+      ```
+
+   {% data reusables.enterprise-migration-tool.reclaim-individual-mannequin %}
+
+      ```shell copy
+      gh gl2gh reclaim-mannequin --github-org DESTINATION --mannequin-user MANNEQUIN --target-user USERNAME
+      ```
+
+{% data reusables.enterprise-migration-tool.mannequin-reclaim-must-accept %}
+
+{% endif %}
+
 ### Reclaiming mannequins in your browser
 
 {% data reusables.elm.reclaim-mannequins-in-browser %}

content/migrations/using-github-enterprise-importer/index.md

@@ -10,6 +10,7 @@ children:
   - /understanding-github-enterprise-importer
   - /migrating-from-bitbucket-server-to-github-enterprise-cloud
   - /migrating-between-github-products
+  - /migrate-from-gitlab
   - /completing-your-migration-with-github-enterprise-importer
 redirect_from:
   - /early-access/github/migrating-with-github-enterprise-importer