Workflow for Automating PR Creation for Release Updates

[AshwinSriram11]

Closes prometheus-operator/prometheus-operator#6877. With this workflow, a PR will be automatically created when the upstream release in prometheus-operator repository does not match the release version in https://github.com/prometheus-operator/website/blob/main/data/prometheusOperator.json.

[ArthurSens]

Discussed this today, some plans for testing:

• Create a new branch and change the operator version to any that we've released in the past
• Update this PR to update that branch instead of main, also add on: dispatch... so we can manually trigger this.
• Merge this PR
• Run workflow, fix it if it fails
• New PR updating workflow target to main
• Profit!!!

[AshwinSriram11]

I am currently testing this on my fork.

[AshwinSriram11]

I am a little stuck. Since it was getting messy, I tried creating a new PR(which has the workflow) from a test-wf branch. I also made another branch called wf, which I changed to a previous version. Then, I merged the PR from test-wf branch to the wf branch in my fork of the repo. I thought I would see the workflow in the Actions page but nothing was there.

Should I create a branch in this repo(not in my fork) and then try to merge a PR on that branch to test this?

[nicolastakashi]

I am a little stuck. Since it was getting messy, I tried creating a new PR(which has the workflow) from a test-wf branch. I also made another branch called wf, which I changed to a previous version. Then, I merged the PR from test-wf branch to the wf branch in my fork of the repo. I thought I would see the workflow in the Actions page but nothing was there.

Should I create a branch in this repo(not in my fork) and then try to merge a PR on that branch to test this?

Yes, AFAIK fork PRs don't trigger builds on the main one.

[AshwinSriram11]

I created a workflow branch and merged the PR in that branch. But still not getting anything on the Actions tab.