myasnikovdaniil
3d12ece2af
Takes over #3433 and finishes it. Closes #2585. The rename itself is IvanHunters' work, replayed here on current main with his commits intact. What was blocking it was my own review, and this fixes that plus one thing that appeared on main afterwards. ## What was blocking it The gate in `backport.yaml` matched `kind/backport` only after the rename. The `aliases:` in `labels.yml` migrate labels already attached to issues and pull requests, but they do not change what an external applier does going forward, and the org-level dosubot still applies the legacy names. So the bot would have quietly stopped firing for the share of backports it labels. Both spellings are now accepted, in the `if:` gate and in the JS step that reads them. ## What appeared afterwards #3569 landed while #3433 sat, and it added a concurrency guard that appends `-label` to the group for any labeled event that is not a backport label, so a backport label never cancels a run already in flight. That guard enumerated the two legacy names, so once the labels are namespaced a `kind/backport` event takes the `-label` branch and the guard stops covering the case it exists for. Extended to the new names. ## The dual acceptance is transitional and says so Accepting two spellings is a bridge, not a design. The plan is to switch dosubot's pull request labelling off and leave the in-repo labeler as the only applier, at which point the legacy arms can go. The comment in the workflow names all three deletion sites so that cleanup is mechanical: the `if:` gate, the JS step, and the concurrency group. Landing this before or after dosubot is switched off both work, which is the point. ## Checks `actionlint` clean on the workflow. There is no bats coverage for this gate on main; #3813 is what adds `hack/pr-labeler-contract.bats`, so the two are worth landing in that order. ### Release note ```release-note NONE ``` <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **Workflow Improvements** - Backport automation now supports standardized `kind/backport` and `kind/backport-previous` labels while maintaining compatibility with legacy labels during the transition. - Stale pull request handling and backport detection now follow the standardized labeling scheme. - **Documentation** - Updated contribution and release documentation with the new labels, labeling requirements, and troubleshooting guidance. - **Tests** - Expanded validation to cover both standardized and legacy backport labels. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
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.