CI: Add upstream-sync workflow #1678
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
Alex-Welsh
reviewed
Jun 3, 2025
We tried adding upstream-sync using stackhpc-release-train [1], but the workflow addition is skipped because our default branch is a StackHPC release branch [2]. Add workflow manually to synchronise releases that still exist upstream. [1] stackhpc/stackhpc-release-train#410 [2] stackhpc/stackhpc-release-train@49c06d1
priteau
force-pushed
the
skc-upstream-sync
branch
from
46c7737 to
bb093ca
Compare
Good catch. I updated the workflow, hopefully with the right syntax? |
Alex-Welsh
approved these changes
Jun 3, 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.
We tried adding upstream-sync using stackhpc-release-train [1], but the workflow addition is skipped because our default branch is a StackHPC release branch [2].
Add workflow manually to synchronise releases that still exist upstream.
[1] stackhpc/stackhpc-release-train#410
[2] stackhpc/stackhpc-release-train@49c06d1