Repository navigation
Conversation
todti
force-pushed
the
ci/allure-ci-app-token
branch
from
September 16, 2026 08:51
486448b to
09480f0
Compare
Contributor
Author
|
Recreating. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mirrors allure-framework/allure-rust#44: the release workflow now mints a short-lived token via
actions/create-github-app-token(allure-ci app) instead of the long-livedQAMETA_CIPAT, and commits as<slug>[bot].Requires org vars
ALLURE_CI_APP_CLIENT_ID,ALLURE_CI_APP_SLUG,ALLURE_CI_APP_USER_IDand secretALLURE_CI_APP_PRIVATE_KEY, plus branch protection bypass/push for the allure-ci app (already configured).Validation: only exercised by an actual
workflow_dispatchrelease run — needs a real release to confirm push + release creation.