Myasnikov Daniil 507336dba0 fix(ci): report "E2E Tests" green on a release promotion PR
Under main's rc-gate model a promote PR carries `release` and deliberately not
`full-e2e`, so the `e2e` job skips: the immutable rc whose digests the tree pins
was already verified, which is the cost the rc gate exists to remove. While the
required gate was a job, that skip satisfied branch protection. Now that it is a
commit status, e2e-report saw PLAN_RESULT=success, CODE=true (a promotion
rewrites ~38 non-docs image refs) and E2E_RESULT=skipped, fell to the last
branch and posted failure — so every release would have needed a full suite
re-run or an admin override of the very gate this PR strengthens.

Give e2e-report the carve-out the `e2e` job already has: release without
full-e2e reports success and says why. Adding full-e2e still forces a real run
and a real verdict.

Close the second route to the same red as well. `gh pr create --label` attaches
the label just after opening, so the `labeled` event cancels the `opened` run
through cancel-in-progress; under always() that dying run still posted failure
with PLAN_RESULT=cancelled, and the `labeled` run replacing it is skipped by the
allow-list guard, so nothing flipped the status back. !cancelled() makes a
cancelled run report nothing, which is the same fail-closed posture used
elsewhere here: not posting leaves the required status "Expected", which blocks.

Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
2026-07-30 11:54:52 +05:00
2025-10-08 09:43:34 +05:00
2025-04-01 18:48:14 +02: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 52%
Shell 34%
TypeScript 6.8%
Go Template 4.7%
Makefile 1.3%
Other 1.1%