Skip to content

Disable upstream sync workflow - #2456

Merged
Alex-Welsh merged 1 commit into
stackhpc/2025.1from
disable-upstream-sync
Jul 29, 2026
Merged

Disable upstream sync workflow#2456
Alex-Welsh merged 1 commit into
stackhpc/2025.1from
disable-upstream-sync

Conversation

@Alex-Welsh

Copy link
Copy Markdown
Member

This workflow should sync SKC with the upstream kayobe-config template. Unfortunately, it has never workedm because it has a different structure to standard openstack forks. Disabling it until we have time to properly investigate it.

This workflow should sync SKC with the upstream kayobe-config template.
Unfortunately, it has never workedm because it has a different structure
to standard openstack forks. Disabling it until we have time to properly
investigate it.
@Alex-Welsh
Alex-Welsh requested a review from a team as a code owner July 27, 2026 09:33
@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

💤 Files selected but had no reviewable changes (1)
  • .github/workflows/upstream-sync.yml
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 372c04a5-a3e9-4e2a-a3ff-cb9f01937c60

📥 Commits

Reviewing files that changed from the base of the PR and between b80fbec and f549254.

📒 Files selected for processing (1)
  • .github/workflows/upstream-sync.yml

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@Alex-Welsh

Copy link
Copy Markdown
Member Author

See also stackhpc/stackhpc-release-train#552

@Alex-Welsh

Copy link
Copy Markdown
Member Author

@jackhodgkiss

Copy link
Copy Markdown
Contributor

It doesn't work because this repository is not in the fork network for openstack/kayobe-config. This repository is https://github.com/stackhpc/kayobe-config.

If we want this fixed we would need to remove the other repository and request for this repository to be added to the fork network of openstack/kayobe-config via GitHub support.

@Alex-Welsh

Copy link
Copy Markdown
Member Author

It doesn't work because this repository is not in the fork network for openstack/kayobe-config. This repository is https://github.com/stackhpc/kayobe-config.

If we want this fixed we would need to remove the other repository and request for this repository to be added to the fork network of openstack/kayobe-config via GitHub support.

Or, we make the upstream repo a variable we can override and just define manually for this repo

@jackhodgkiss

Copy link
Copy Markdown
Contributor

It doesn't work because this repository is not in the fork network for openstack/kayobe-config. This repository is https://github.com/stackhpc/kayobe-config.
If we want this fixed we would need to remove the other repository and request for this repository to be added to the fork network of openstack/kayobe-config via GitHub support.

Or, we make the upstream repo a variable we can override and just define manually for this repo

That won't work I made the upstream sync workflow depend heavily on fork networks as it allows you to use the GitHub API to open PRs with branches from other repositories within the network.

@Alex-Welsh
Alex-Welsh merged commit d02d05d into stackhpc/2025.1 Jul 29, 2026
36 checks passed
@Alex-Welsh
Alex-Welsh deleted the disable-upstream-sync branch July 29, 2026 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

waiting-review PR is waiting for a review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants