Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(release-workflows): reworded some details about the release workflow for clarity #3263

Merged
merged 1 commit into from Apr 29, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion SUMMARY.md
Expand Up @@ -7,7 +7,7 @@
- [CI Configuration](docs/usage/ci-configuration.md)
- [Configuration](docs/usage/configuration.md)
- [Plugins](docs/usage/plugins.md)
- [Workflow configuration](docs/usage/workflow-configuration.md)
- [Release Workflow configuration](docs/usage/workflow-configuration.md)
- [Shareable configurations](docs/usage/shareable-configurations.md)

## Extending
Expand Down
13 changes: 7 additions & 6 deletions docs/usage/workflow-configuration.md
@@ -1,11 +1,12 @@
# Workflow configuration
# Release Workflow configuration

**semantic-release** allow to manage and automate complex release workflow, based on multiple Git branches and distribution channels. This allow to:
**semantic-release** enables managing and automating complex release workflow, based on multiple Git branches and distribution channels.
This enables:

- Distribute certain releases to a particular group of users via distribution channels
- Manage the availability of releases on distribution channels via branches merge
- Maintain multiple lines of releases in parallel
- Work on large future releases outside the normal flow of one version increment per Git push
- Distributing certain releases to a particular group of users via distribution channels
- Managing the availability of releases on distribution channels via branches merge
- Maintaining multiple lines of releases in parallel
- Working on large future releases outside the normal flow of one version increment per Git push

See [Release workflow recipes](../recipes/release-workflow/README.md#release-workflow) for detailed examples.

Expand Down