mirror of
https://github.com/goreleaser/goreleaser.git
synced 2025-01-26 04:22:05 +02:00
01fd3e8c7b
* feat: support closing milestones Reference: https://github.com/goreleaser/goreleaser/issues/1415 * refactor: Adjust milestone handling for code simplification, add ErrNoMilestoneFound, and fix milestone documentation close default Reference: https://github.com/goreleaser/goreleaser/pull/1657#pullrequestreview-445025743 * refactor: Use single repo config in milestones instead of each VCS * fix: Ensure milestone Pipe is included in Defaulters * feat: Add fail_on_error configuration to milestone configuration Co-authored-by: Radek Simko <radek.simko@gmail.com>
36 lines
772 B
Markdown
36 lines
772 B
Markdown
---
|
|
title: Milestone
|
|
---
|
|
|
|
GoReleaser can close repository milestones after successfully
|
|
publishing all artifacts.
|
|
|
|
Let's see what can be customized in the `milestones` section:
|
|
|
|
```yaml
|
|
# .goreleaser.yml
|
|
milestones:
|
|
# You can have multiple milestone configs
|
|
-
|
|
# Repository for the milestone
|
|
# Default is extracted from the origin remote URL
|
|
repo:
|
|
owner: user
|
|
name: repo
|
|
|
|
# Whether to close the milestone
|
|
# Default is false
|
|
close: true
|
|
|
|
# Fail release on errors, such as missing milestone on close
|
|
# Default is false
|
|
fail_on_error: true
|
|
|
|
# Name of the milestone
|
|
# Default is `{{ .Tag }}`
|
|
name_template: "Current Release"
|
|
```
|
|
|
|
!!! tip
|
|
Learn more about the [name template engine](/customization/templates).
|