NO-JIRA: chore(make) move downstream specific files to openshift folder

[matzew]

@nader-ziada moving the file to a better sub-folder

@Cali0707 the recent (manual) syncs you did not use this, right?

[openshift-ci-robot]

@matzew: This pull request explicitly references no jira issue.

Details

In response to this:

@nader-ziada moving the file to a better sub-folder

@Cali0707 the recent (manual) syncs you did not use this, right?

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: matzew

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [matzew]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Cali0707]

@Cali0707 the recent (manual) syncs you did not use this, right?

Yes, I used my own script recently (without any of the gh cli bits):

git fetch upstream
git fetch downstream
git checkout downstream/main
git switch -c sync-downstream
git merge upstream/main --no-commit
git commit -s -m "chore(sync): merge upstream into downstream"
go mod tidy
go mod vendor
git add vendor/
git commit -s -m "chore(deps): vendor updated deps after sync"

[matzew]

I have similar script, @Cali0707 - I also rely on the downstream origin (for openshift/openshift-mcp-server)

[openshift-ci]

@matzew: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[nader-ziada]

this is lgtm