@@ -96,7 +96,7 @@ jobs:
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
- name: Validate Gradle wrapper
|
||||
uses: gradle/wrapper-validation-action@ccb4328a959376b642e027874838f60f8e596de3
|
||||
- name: Publish package
|
||||
@@ -172,7 +172,7 @@ jobs:
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
- name: Validate Gradle wrapper
|
||||
uses: gradle/wrapper-validation-action@ccb4328a959376b642e027874838f60f8e596de3
|
||||
- name: Publish package
|
||||
@@ -256,7 +256,7 @@ jobs:
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
- name: Validate Gradle wrapper
|
||||
uses: gradle/wrapper-validation-action@ccb4328a959376b642e027874838f60f8e596de3
|
||||
- name: Publish package
|
||||
|
||||
@@ -88,7 +88,7 @@ jobs:
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
server-id: ossrh
|
||||
server-username: MAVEN_USERNAME
|
||||
server-password: MAVEN_PASSWORD
|
||||
@@ -154,7 +154,7 @@ jobs:
|
||||
- uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
- name: Publish package
|
||||
run: mvn --batch-mode deploy
|
||||
env:
|
||||
@@ -192,7 +192,7 @@ jobs:
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
server-id: ossrh
|
||||
server-username: MAVEN_USERNAME
|
||||
server-password: MAVEN_PASSWORD
|
||||
@@ -205,7 +205,7 @@ jobs:
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
- name: Publish to GitHub Packages
|
||||
run: mvn --batch-mode deploy
|
||||
env:
|
||||
|
||||
@@ -116,7 +116,9 @@ You can establish role-based access control for users from your LDAP server by s
|
||||
|
||||
{% note %}
|
||||
|
||||
**Note:** If you use Active Directory, user lookups and team synchronization may fail when the LDAP groups configured for teams or in the {% data variables.enterprise.management_console %} exceed 1500 members, due to the `MaxValRange` limit in Active Directory. As a workaround, you can use Active Directory groups that contain less than 1500 members, or you can work with your Active Directory administrator to increase the `MaxValRange` value for your domain controllers. For more information, see [View and set LDAP policy in Active Directory by using Ntdsutil.exe](https://learn.microsoft.com/en-US/troubleshoot/windows-server/identity/view-set-ldap-policy-using-ntdsutil) in Microsoft Learn.
|
||||
**Note:** Using LDAP Synchronization with groups that exceed 1499 members may lead to team membership synchronization failures.
|
||||
|
||||
If you use Active Directory specifically, user lookups and team synchronization may fail when the LDAP groups configured for teams or in the {% data variables.enterprise.management_console %} exceed 1500 members, due to the `MaxValRange` limit in Active Directory. As a workaround, you can use Active Directory groups that contain less than 1500 members, or you can work with your Active Directory administrator to increase the `MaxValRange` value for your domain controllers. For more information, see [View and set LDAP policy in Active Directory by using Ntdsutil.exe](https://learn.microsoft.com/en-US/troubleshoot/windows-server/identity/view-set-ldap-policy-using-ntdsutil) in Microsoft Learn.
|
||||
|
||||
If you need help determining if modifying the `MaxValRange` is the right approach for your Active Directory environment, contact Microsoft Support.
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@
|
||||
|
||||
The starter workflow sets up the `PATH` to contain OpenJDK 8 for the x64 platform. If you want to use a different version of Java, or target a different architecture (`x64` or `x86`), you can use the `setup-java` action to choose a different Java runtime environment.
|
||||
|
||||
For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'adopt'` and `x64`.
|
||||
For example, to use version 11 of the JDK provided by Adoptium for the x64 platform, you can use the `setup-java` action and configure the `java-version`, `distribution` and `architecture` parameters to `'11'`, `'temurin'` and `x64`.
|
||||
|
||||
```yaml copy
|
||||
steps:
|
||||
@@ -11,7 +11,7 @@ steps:
|
||||
uses: {% data reusables.actions.action-setup-java %}
|
||||
with:
|
||||
java-version: '11'
|
||||
distribution: 'adopt'
|
||||
distribution: 'temurin'
|
||||
architecture: x64
|
||||
```
|
||||
|
||||
|
||||
@@ -12,6 +12,12 @@ Currently, the following data is **not** migrated.
|
||||
- Any {% data variables.product.prodname_projects_v2 %} (the new projects experience)
|
||||
- Discussions at the repository level
|
||||
- Packages in {% data variables.product.prodname_registry %}
|
||||
- GitHub Apps
|
||||
- GitHub Apps and GitHub App installations
|
||||
- Fork relationships between repositories (see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks)")
|
||||
- References between pull requests and issues in different repositories (see "[AUTOTITLE](/get-started/writing-on-github/working-with-advanced-formatting/autolinked-references-and-urls)")
|
||||
- Tag protection rules
|
||||
- Repository stars
|
||||
- Repository watchers
|
||||
- Commit status checks
|
||||
- Edit history of issue comments and pull request comments
|
||||
- Users' profiles, SSH keys or signing keys
|
||||
Reference in New Issue
Block a user