openshift
[DPTP-4326] Updated branches references from "master" to "main"
Various references of master branch was renamed to main, this include:
- The minimum tests possible;
- References to
openshift/release@masterand; - Default branch names used by some tools.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: hector-vido
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [hector-vido]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
This change needs to be announced to the public and it should be merged right after you rename the branches on o/release and o/ci-tools. I would even announce it beforehand (on XX of March we will rename branches, expect outage for X hours)
Our team (CRT) is working to get openshift repos renamed from 'master' to 'main' (working with repo owners who have a better understanding of the consequences of the rename that we do) but I don't know who is planning to do the openshift/release default branch rename.
We think that the o/release repo will be one of the last (if not the very last) repo to rename. As I expect the effects to be broad (though I admit I don't really know how broad), I agree with @Prucek that we will, at the very least, need to announce it with sufficient notice and have some kind of revert/backout/mitigation plan if things go sideways.
@hector-vido: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/breaking-changes | 1485859a1a313ed44beb9ba89cc4e9e21cdcda7f | link | false | /test breaking-changes |
| ci/prow/unit | 1485859a1a313ed44beb9ba89cc4e9e21cdcda7f | link | true | /test unit |
| ci/prow/integration | 1485859a1a313ed44beb9ba89cc4e9e21cdcda7f | link | true | /test integration |
| ci/prow/images | 1485859a1a313ed44beb9ba89cc4e9e21cdcda7f | link | true | /test images |
Full PR test history. Your PR dashboard.
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
PR needs rebase.
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.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale