Skip to content

chore(merge-*): restore downstream files and drop upstream .github/workflows post-merge - #163

Merged
machine424 merged 2 commits into
rhobs:mainfrom
machine424:alertoo
Sep 3, 2026
Merged

chore(merge-*): restore downstream files and drop upstream .github/workflows post-merge#163
machine424 merged 2 commits into
rhobs:mainfrom
machine424:alertoo

Conversation

@machine424

@machine424 machine424 commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

Add .ci-operator.yaml, Dockerfile.ocp and OWNERS to restore-downstream for all non-ACM merge workflows so downstream-specific files are preserved on merge conflicts.

Remove .github/ and .github/workflows/ from restore-upstream where they were (kube-state-metrics, resource-state-metrics, node-exporter).

Delete upstream CI workflows and dependabot.yml post-merge (in merge-flow.yaml) as they are unused downstream and trigger unwanted security/dependabot alerts.

Fixes alertmanager merger broken by a conflict in .github/workflows/build-release-branch.yml.

Ref: https://github.com/rhobs/syncbot/actions/runs/32792840276

@machine424
machine424 requested a review from a team as a code owner August 25, 2026 18:39
@machine424 machine424 changed the title chore(merge-*): restore downstream .github/, OWNERS, Dockerfile.ocp and .ci-operator.yaml on conflicts WIP: chore(merge-*): restore downstream .github/, OWNERS, Dockerfile.ocp and .ci-operator.yaml on conflicts Aug 25, 2026
@machine424 machine424 changed the title WIP: chore(merge-*): restore downstream .github/, OWNERS, Dockerfile.ocp and .ci-operator.yaml on conflicts chore(merge-*): add restore-downstream for .github/workflows/, OWNERS, Dockerfile.ocp and .ci-operator.yaml Aug 25, 2026
… .ci-operator.yaml

Add these to restore-downstream for all non-ACM merge workflows so
downstream-specific files are preserved on merge conflicts.

Also remove .github/ and .github/workflows/ from restore-upstream
where they were (kube-state-metrics, resource-state-metrics,
node-exporter) since upstream .github/ is not needed downstream.

Fixes alertmanager merger broken by a conflict in
.github/workflows/build-release-branch.yml.

Ref: https://github.com/rhobs/syncbot/actions/runs/32792840276
…onfig post-merge

Upstream CI workflows and dependabot.yml are unused downstream and
can trigger unwanted security/dependabot alerts. Delete them
post-merge instead of restoring them via restore-downstream.
@machine424 machine424 changed the title chore(merge-*): add restore-downstream for .github/workflows/, OWNERS, Dockerfile.ocp and .ci-operator.yaml chore(merge-*): restore downstream files and drop upstream .github/workflows post-merge Sep 1, 2026
redhat-chai-bot added a commit to redhat-chai-bot/openshift_prometheus-alertmanager that referenced this pull request Sep 1, 2026
The upstream GitHub Actions workflows are not used downstream
(OpenShift CI uses Prow/ci-operator). The syncbot is being updated
(rhobs/syncbot#163) to drop .github/workflows post-merge, so
removing it now avoids merge conflicts.
restore-downstream: OWNERS
restore-downstream: >-
.ci-operator.yaml
Dockerfile.ocp

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These two exists only downstream, it wont cause merge conflict IIUC. Any reason you think it should be here?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just to be safe, no matter what happens, we want those downstream files there.

@machine424
machine424 merged commit 28c38ef into rhobs:main Sep 3, 2026
9 of 12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants