Myasnikov Daniil 900fc0e2e5 chore(ci): read only the namespaced backport labels
The un-namespaced `backport` and `backport-previous` were accepted
alongside `kind/backport` and `kind/backport-previous` so that the rename
could land in any order relative to the org-level dosubot, which was
then the dominant applier on real backports. Both conditions for
dropping them now hold: dosubot no longer labels PRs here -- every
backport label applied in the last month came from a maintainer -- and
.github/labels.yml has renamed the labels themselves, so neither legacy
name exists in the repository and the picker offers only the namespaced
pair.

Three sites went together, because a half-finished rename is worse than
either end of it: the concurrency group key, `prepare`'s `if:` gate, and
the `Check which labels are present` step. A name dropped from one and
not the others either routes a genuine request into a group it must
queue behind, or qualifies a run that then finds no target.

The aliases stay in .github/labels.yml on purpose. An alias is not a
label, so nothing offers a legacy name; what it does is make the next
label sync rename a stray back into kind/*, carrying its PRs with it,
rather than leaving a dead label that triggers nothing and that nothing
ever cleans up. That sync is weekly, which docs/release.md now states
alongside the accepted spellings.

Assisted-By: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-09-03 11:56:38 +05:00
2025-10-08 09:43:34 +05:00
2024-02-08 12:04:32 +01:00

Cozystack Cozystack

Open Source Apache-2.0 License Support Active GitHub Release GitHub Commit OpenSSF Best Practices OpenSSF Scorecard

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.

Cozystack user interface

Use-Cases

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.

Languages
Go 47.2%
Shell 37.6%
TypeScript 7%
Go Template 5.4%
Makefile 1.4%
Other 1.2%