Skip to content

Conversation

kandersolar
Copy link
Member

Similar to #1531, this makes new GitHub Secrets available to the pytest remote-data workflow. This must be done separately from the PRs that want to use the secrets (#2572, #2573) because (quoting #1497 (comment)):

I think it is just the annoying but secure behavior of pull-request-target not respecting yml changes in the PR -- your update to include the SA key in the environment isn't taking effect because the action is defined by the .github/workflows/pytest-remote-data.yml file on master, not this PR branch. I guess the cleanest workaround is to submit a separate PR to change pytest-remote-data.yml, merge that, then merge master into this PR?

@kandersolar kandersolar added this to the v0.13.2 milestone Oct 17, 2025
@kandersolar kandersolar added the build tools Pipelines, CI, GH actions label Oct 17, 2025
@kandersolar kandersolar merged commit 5b41b3f into main Oct 17, 2025
28 checks passed
@kandersolar kandersolar deleted the kandersolar-patch-1 branch October 17, 2025 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build tools Pipelines, CI, GH actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants