Add if: always() to upload-artifact step in awsfulltest workflow
#49
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.
This PR adds the
if: always()condition to the upload-artifact step in the AWS full test workflow to ensure that Seqera Platform debug logs are always uploaded, even when previous steps fail.Problem
Currently, when the "Launch workflow via Seqera Platform" step fails in the AWS full test workflow, the subsequent artifact upload step is skipped. This makes debugging failures difficult because the Seqera Platform debug log files (
seqera_platform_action_*.logandseqera_platform_action_*.json) are not available for inspection.Solution
Added
if: always()to theupload-artifactstep (line 65 in.github/workflows/awsfulltest.yml). This ensures that the debug logs are uploaded regardless of whether the previous steps succeed or fail.Changes
.github/workflows/awsfulltest.yml: Addedif: always()condition to the upload-artifact stepThis is a common best practice in GitHub Actions workflows to ensure troubleshooting information is always available when debugging workflow failures.
Fixes https://github.com/nf-core/denovotranscript/actions/runs/17119887222
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.