Myasnikov Daniil
1b8b9f43ec
Forgetting the `backport` label costs a release-branch fix; removing a label during review costs a click. So invert the default: a PR whose Conventional Commits type is `fix` gets `backport` on arrival, and a maintainer who decides it must not reach a release line removes it. The removal has to stick, which is what shapes the condition. This workflow also runs on `reopened` and `synchronize`, so re-applying the label the way `kind/*` and `area/*` are re-applied would bring it back with the next push and make removal fiction — worse than no default, because it would look like it works. `kind/*` and `area/*` are derivations from the title and a human removing one is removing a fact; `backport` is a human decision with a default. It is therefore seeded only on `opened`, which fires exactly once per PR, and never again. `reopened` is excluded on the same grounds: a reopen follows a close, by which point the label has usually been considered. Three exclusions. A backport PR itself, reusing the `[Backport ...]` detector already in the file rather than adding a second one — auto labeling those is what caused recursive backports. A breaking change, which must never default into a patch release line. And nine scopes whose code is main-only or where a cherry-pick is meaningless: ci, e2e, tests, build, deps, agents, release, backport, migrations. `migrations` is preventive rather than observed — it is in no recent PR title — but a migration backported without diffing the version slot across branches makes the newer branch silently skip its own migration at that slot. On a composite scope any excluded part suppresses the label, rather than requiring all of them to be excluded: `fix(platform,ci)` is exactly the shape that drags main-only content into a release branch. What the default does not buy is stated in the file. backport.yaml's `conflict_resolution: draft_commit_conflicts` covers a conflict; it cannot cover a backport that applies cleanly and wrongly, because the action imports whole files the target branch lacks. The reviewer still owns whether the change belongs on the release line. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.