# https://github.com/tensorflow/tensorflow/actions/workflows/release-branch-cherrypick.yml
# and click "Run Workflow." Leave "Use Workflow From" set to "master", then
# input the branch name and paste the cherry-pick commit and click Run. A PR
# will be created.

name: Release Branch Cherrypick
on:
  workflow_dispatch:
    inputs:
      # We use this instead of the "run on branch" argument because GitHub looks

    triggerRules = "+:root=${branch.vcsRootId()}:."
    branchFilter = "+:<default>"
}

class PublishNightlySnapshot(
    branch: VersionedSettingsBranch,
) : PublishGradleDistributionFullBuild(
        promotedBranch = branch.branchName,
        prepTask = branch.prepNightlyTaskName(),
        promoteTask = branch.promoteNightlyTaskName(),
        triggerName = "ReadyforNightly",
    ) {

        val triggerName = this.triggerName

        params {
            text(
                "branch.qualifier",
                "%dep.${RelativeId("Check_Stage_${triggerName}_Trigger")}.teamcity.build.branch%",
                label = "Branch qualifier for the published distribution version",

# computes a hash of a remote repo's tag state.
# Tag definitions can come from the .hgtags file stored in
# any head of any branch, and the server protocol does not
# expose the tags directly. However, the protocol does expose
# the hashes of all the branch heads, so we can use a hash of
# all those branch names and heads as a conservative snapshot
# of the entire remote repo state, and use that as the tag sum.

        buildType(PublishNightlySnapshotFromQuickFeedbackStepPromote(branch))
        buildType(PublishBranchSnapshotFromQuickFeedback)
        buildType(PublishMilestone(branch))

        if (branch.isMaster) {
            buildType(StartReleaseCycle)
            buildType(StartReleaseCycleTest)
        } else {
            buildType(PublishReleaseCandidate(branch))

        description =
            "Promotes the latest successful documentation changes on '${branch.branchName}' from Ready for Nightly as a new nightly documentation snapshot"

        triggers {
            branch.determineNightlyPromotionTriggerHour()?.let { triggerHour ->
                schedule {
                    scheduledTrigger(branch, policy = daily { this.hour = triggerHour }, pendingChangesOnly = true)
                }
            }

 */

package promotion

import common.VersionedSettingsBranch

class PublishNightlySnapshotFromQuickFeedbackStepPromote(
    branch: VersionedSettingsBranch,
) : BasePublishGradleDistribution(
        promotedBranch = branch.branchName,
        prepTask = branch.prepNightlyTaskName(),
        triggerName = "QuickFeedback",
        cleanCheckout = false,
    ) {
    init {

        cleanup {
            history(days = 180)
        }

        this.init()
    }
}

class PublishFinalRelease(
    branch: VersionedSettingsBranch,
) : PublishRelease(
        promotedBranch = branch.branchName,
        prepTask = "prepFinalRelease",
        promoteTask = branch.promoteFinalReleaseTaskName(),
        requiredConfirmationCode = "final",
        init = {
            id(FINAL_RELEASE_BUILD_CONFIGURATION_ID)

        }

        if (generateTriggers) {
            val enableTriggers = model.branch.isMainBranch || model.branch.isLegacyRelease
            if (stage.trigger == Trigger.EACH_COMMIT) {
                val effectiveTriggerBranches = mutableListOf(model.branch.branchName)

                if (model.branch.isMaster) {
                    effectiveTriggerBranches.add(PROVIDER_API_MIGRATION_BRANCH)

 *
 * When merging `releaseX` branch into `master`, we should only use the release note from the `master` branch,
 * but sometimes changes on release notes.md was brought to master and merged unnoticed,
 * e.g https://github.com/gradle/gradle/pull/25825
 *
 * This script is to check if there is any merge commit that brings changes from release branch to master.
 * Usage: groovy CheckBadMerge.groovy <commit1> <commit2> ...