Write files for release to single directory #140
Merged
Conversation
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
To allow us to automate release requests for this workspace, write the file to be released (report.html) and the supporting file (latest_import_dates.csv) to the same containing directory. This means we can set up the release request so that both output and supporting files are added to the same group.
rebkwok
force-pushed
the
prep-for-automated-releases
branch
from
a95155e to
2e4488b
Compare
evansd
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To allow us to automate release requests for this workspace, write the file to be released (report.html) and the supporting file (latest_import_dates.csv)
to the same containing directory. This means we can set up the release request so that both output and supporting files are added to the same group.
Fixes #138
Requires Airlock PR to allow supporting files before the actual automated release can be set up.