-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docs/Tools/CI: Update references from master
to trunk
#28433
Conversation
Size Change: 0 B Total Size: 1.39 MB ℹ️ View Unchanged
|
packages/env/README.md
Outdated
@@ -475,7 +475,7 @@ This is useful for plugin development when upstream Core changes need to be test | |||
|
|||
```json | |||
{ | |||
"core": "WordPress/WordPress#master", | |||
"core": "WordPress/WordPress#trunk", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no trunk
branch in the WordPress repository. It has to stay unchanged.
@ockham and @youknowriad – it touches release scripts, can you do sanity check? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed one place that has to remain unchanged. Everything else looks good.
69e7b9c
to
5577c94
Compare
Rebased and fixed the issue you spotted @gziolo, thanks. |
5577c94
to
e6c9002
Compare
e6c9002
to
54c0a73
Compare
changelog.txt
Outdated
@@ -7659,7 +7659,7 @@ Add knobs to the [ColorIndicator Story](https://github.com/WordPress/gutenberg/p | |||
* Fix keyboard interaction (up/down arrow keys) causing focus to transfer out of the default block’s insertion menu. | |||
* Fix regression causing dynamic blocks not rendering in the frontend. | |||
* Fix vertical alignment issue on Media & Text block. | |||
* Fix some linter errors in master branch. | |||
* Fix some linter errors in main branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this is an oversight, or it's on purpose (because at the time, it wasn't called trunk
?) 🤔 (If the latter, then we'd also need to change the other occurrences in the changelog, no?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intentionally changed it to "main branch" to avoid ever having to change it again in the future, but that seems unlikely so I'll change it to be trunk explicitly.
One minor note here: #28433 (comment). Looking great overall -- thanks for taking care of this! |
b839911
to
1b7a155
Compare
@ockham Do you think we need to backport this to the release/10.1 branch (since it already branched for the RC), to make the scripts there work properly? |
@@ -121,7 +121,7 @@ function parseSourceString( sourceString, { workDirectoryPath } ) { | |||
return { | |||
type: 'git', | |||
url: `https://github.com/${ gitHubFields[ 1 ] }/${ gitHubFields[ 2 ] }.git`, | |||
ref: gitHubFields[ 5 ] || 'master', | |||
ref: gitHubFields[ 5 ] || 'trunk', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This shouldn't be changed I think.
The |
bd6224d
to
73ccaf4
Compare
merged and cherry-picked this to release/10.1 |
Should only be merged AFTER the main branch is renamed to
trunk
All the CI scripts are going to be broken for this PR because the
trunk
branch doesn't exist yet 😉Description
Update references from
master
totrunk
in:How has this been tested?
TBD
Types of changes
Non-breaking changes (renamed functions are all internal)
Checklist: