Add data export flow to current workflow#23
Closed
swu4bnl wants to merge 1 commit into
Closed
Conversation
Closed
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
2 participants
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.
Combines the remaining data-sync work from PR #3 onto the current main branch, which already includes the merged changes from PR #1 and PR #4.\n\nChanges:\n- Adds the export flow from PR #3, updated to use the current API-key based Tiled access pattern.\n- Wires export into the existing end-of-run workflow without removing linker, validation, Slack, or dry-run behavior.\n\nValidation:\n- git diff --check passed.\n- Python/Pixi tests could not be run locally on Windows because this workspace only supports linux-64 in pixi.toml and no Python executable is installed on PATH.