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)
                }
            }

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

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

Keep class names, function names, modules, file names, and CLI commands unchanged.

### List of English terms and their preferred French translations

 */

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)

# 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.

### Traduções

- [English](../../README.md)
- [日本語 (Japanese)](../ja/README.md)
- [简体中文 (Simplified Chinese)](../zh-CN/README.md)
- [Español (Spanish)](../es/README.md)
- [Français (French)](../fr/README.md)
- [Deutsch (German)](../de/README.md)
- [한국어 (Korean)](../ko/README.md)

## Desenvolvido por

* [Lasta Di](https://github.com/lastaflute/lasta-di "Lasta Di"): Contêiner DI

 */

package promotion

import common.VersionedSettingsBranch

class PublishNightlySnapshotFromQuickFeedbackStepUpload(
    branch: VersionedSettingsBranch,
) : BasePublishGradleDistribution(
        promotedBranch = branch.branchName,
        prepTask = branch.prepNightlyTaskName(),
        triggerName = "QuickFeedback",
    ) {
    init {
        id("Promotion_SnapshotFromQuickFeedbackStepUpload")

based on a specific branch. Currently, we have two pipelines: `master` and `release`, but you can easily create
and test another isolated pipeline from any branch. 

We'll explain everything via an example. Let's say you make some changes on your branch `myTestBranch`
(we highly recommend to name this branch without prefix and hyphen (`-`) because it's used to generate build type ID) and want to

	<property name="mydbflute.dir" value="${basedir}/mydbflute" />
	<property name="target.dir" value="${basedir}/target" />
	<property name="branch.name" value="fess-15.4" />
	<property name="mydbflute.url" value="https://github.com/lastaflute/lastaflute-example-waterfront/archive/${branch.name}.zip" />

	<target name="mydbflute.check">
		<condition property="mydbflute.exists">
			<available file="${mydbflute.dir}" type="dir" />