chore: retarget master branch refs to main#5538
Draft
nabramovitz wants to merge 2 commits into
Draft
Conversation
Prepares for the master -> main release-branch rename: - workflow triggers (pr, stb_tests, backend_tests, frontend_tests, documentation) now target main - console-sync-release pipeline + secrets sample branch refs - Chart.yaml icon raw URL (raw URLs do not redirect on rename) - package.json climate script diff base - .travis.yml branch allowlist (v2-master left as-is) - docs: release_guide, contributing guides, developer-environment, devops_guide, cf-api-v2-usage, README license badge - CONTRIBUTING.md: corrected stale claim that PRs target master (they target develop; main is the release branch) Other projects' master URLs (helm, gimme, mo, mariadb, angular-cli, monocular) and historical CHANGELOG entries are untouched.
The docs tree merged in cloudfoundry#5547 arrived after this branch was cut and carries its own cloudfoundry/stratos tree/master and blob/master links. Same treatment as the rest of the branch; SUSE and third-party repo links are left alone.
nabramovitz
force-pushed
the
norm/chore/main-release-branch
branch
from
eb52ce8 to
d1c675f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
⚠ Merge after the rename
Draft until the
master→mainrename executes (requested from org admins in cloudfoundry/community#1544; protection pre-staged in cloudfoundry/community#1537). Merging early would point the chart icon raw URL at a branch that doesn't exist yet. Once the rename lands, this should merge promptly — develop'smasterrefs (icon raw URL, workflow triggers) break at rename time until it does.Closes #5507
What
Swaps every in-repo reference to stratos's own
masterbranch over tomain:pr.yml,stb_tests.yml,backend_tests.yml,frontend_tests.yml,documentation.ymldeploy/ci/console-sync-release.yml(branch: master) +deploy/ci/secrets.yml-samplebranch defaultsdeploy/kubernetes/console/Chart.yamlicon raw URL — the one mandatory link fix (raw.githubusercontent URLs do not redirect on branch rename; blob/tree web URLs do)package.jsonclimatescript diff base.travis.ymlbranch allowlist (v2-masterleft as-is — that branch still exists)release_guide.md(release flow now cuts frommain),contributing_guide.md,developer-environment.md,devops_guide.md,cf-api-v2-usage.md, README license badgeCONTRIBUTING.md: also fixes the stale claim that PRs targetmaster—developis the PR target;mainis the release lineDeliberately untouched
Other projects'
masterURLs (helm, gimme, mo, mariadb, angular-cli, monocular, golang/dep), historical CHANGELOG entries, "master/detail" UI-pattern comments, the e2e branch-name matcher (already accepts both), and the codecov badge (points at the cloudfoundry-community fork).All edited YAML validated. 17 files, 34 substitutions.