}

    @Internal
    protected
    fun getContributorsFromPullRequests(): Set<GitHubUser> {
        if (!milestone.isPresent) {
            error("Milestone not set: please rerun the task with `--milestone <milestone>`")
        }
        val prs: MutableList<GitHubPullRequest> = mutableListOf()
        for (page in 1..10) {

        assertOrder(X_EQ_Y, "1.beta", "1.BETA");
        assertOrder(X_EQ_Y, "1.beta", "1.Beta");

        assertOrder(X_EQ_Y, "1.milestone", "1.MILESTONE");
        assertOrder(X_EQ_Y, "1.milestone", "1.Milestone");

        assertOrder(X_EQ_Y, "1.rc", "1.RC");
        assertOrder(X_EQ_Y, "1.rc", "1.Rc");
        assertOrder(X_EQ_Y, "1.cr", "1.CR");

                Missed in notes:$contributorsInPullRequestsButNotInReleaseNotes

                You can run `GITHUB_TOKEN=<YourGitHubToken> ./gradlew docs:updateContributorsInReleaseNotes --milestone <milestone>` to update the release notes with correct contributors automatically.
                """.trimIndent()
            )
        }
    }

    prepTask = "prepMilestone",
    promoteTask = branch.promoteMilestoneTaskName(),
    requiredConfirmationCode = "milestone",
    init = {
        id("Promotion_Milestone")
        name = "Release - Milestone"
        description = "Promotes the latest successful change on '${branch.branchName}' as a new milestone"
    }

permissions: {}

jobs:
  check_issue_metadata:
    permissions:
      issues: write
    runs-on: ubuntu-latest
    steps:
      # Check that issues have proper metadata: labels and milestone
      # https://github.com/gradle/issue-management-action/blob/main/src/issue-metadata.ts

Each issue is ultimately part of an epic.

- **Milestone**. Each issue is assigned a milestone. This is 0.1, 0.2, ..., or 'Nebulous Future'. The milestone indicates when we
think the issue should get addressed.

permissions: {}

jobs:
  check_pull_metadata:
    permissions:
      issues: write
      pull-requests: write
    runs-on: ubuntu-latest
    steps:
      # Check that PRs have proper metadata: labels and milestone
      # https://github.com/gradle/issue-management-action/blob/main/src/pull-metadata.ts

            It will be closed in 14 days if no further activity occurs.
            If you don't want the stale bot to close it, then set a milestone for it.
          days-before-pr-close: 14
          close-pr-message: >

            "release, promoteReleaseMilestone"
        ]
    )
    fun `publish milestone build type runs three gradle invocations`(branch: String, promoteTaskName: String) {
        val model = setupModelFor(branch)
        val nightlySnapshot = model.findBuildTypeByName("Release - Milestone")

        val steps = nightlySnapshot.steps.items
        assertEquals(3, steps.size)

        checkVersionsEqual("1.0.0x", "1-x");
        checkVersionsEqual("1cr", "1rc");

        // special "aliases" a, b and m for alpha, beta and milestone
        checkVersionsEqual("1a1", "1-alpha-1");
        checkVersionsEqual("1b2", "1-beta-2");
        checkVersionsEqual("1m3", "1-milestone-3");

        // case insensitive
        checkVersionsEqual("1X", "1x");
        checkVersionsEqual("1A", "1a");