deivydasp/Allure Deployer Action

Deploy Allure reports to GitHub Pages with History, Aggregation and Slack integration

Trust Signals

Scorecard Score: not yet scored
Maintenance Recency: Activelast commit Jun 22, 2026
License: BSD

Pinned Snippet

workflow.ymlSHA-pinned

uses: deivydasp/allure-deployer-action-v2@43e213800f85b25e2ddff6f3645f9ed2f3e12c29 # no releases — HEAD as of 2026-07-11

tags can be moved; commit SHAs can't. why a SHA?

Inputs

name	description	required	default
mode	Action mode. 'deploy' generates and deploys a report. 'summary' reads deployed reports from gh-pages and writes a combined job summary table.	—	deploy
summary	Write a GitHub Actions job summary after deployment. Set to 'false' to skip when using a separate summary job.	—	true
prefixes	Comma-separated list of prefixes to include in summary mode. If omitted, all prefix directories on gh-pages are scanned.	no	—
prefix	Prefix to uniquely identify test report artifacts. Used for summary page, redirect page, rerun tracking, and summary mode.	no	allure-report
gh_artifact_prefix	Prefix to uniquely identify test report artifacts when managing multiple projects.	no	—
report_name	Title of your report	no	—
allure_results_path	A path/to/results or comma separate paths (path/to/results1,path/to/results2) of Allure results. Required in deploy mode.	no	—
show_history	Show history in the test report (true/false)	—	true
pr_comment	Post test report information as pull request comment. Requires `github_token` to be set with permission	—	true
custom_report_dir	A custom directory to generate Allure report into.	no	—
github_token	Auto-generated GITHUB_TOKEN or Personal Access Token for deploying report to GitHub pages and posting report info on pr_comment	—	${{ github.token }}
github_pages_branch	Target branch for Deploying to GitHub Pages. Default: gh-pages	—	gh-pages
language	Allure report language	no	—
github_pages_repo	Another GitHub owner/repo to deploy GitHub pages. Ensure that 'github_token' provided has permissions to the repository	—	${{ github.repository }}
keep	Number of test reports you want to keep alive	—	10
fail_on_test_failure	Fail the action after deployment if any tests failed or broken. Report is always deployed first.	—	false

Outputs

name	description
report_url	URL to your test report
summary_page_url	URL to the summary landing page (available when prefix is set)