Skip to content

Conversation

@desrosj
Copy link
Member

@desrosj desrosj commented Nov 13, 2025

This new post-branching task is meant for any tasks that should be run immediately after creating a new numbered branch. Currently, this only consists of GitHub Actions-related tasks.

In addition to the pre-existing replace:workflow-references-local-to-remote task, a new clean:workflows task is being added that deletes the workflow files that are only intended for trunk.

See 983db64 for the commit showing post-branching changes for the 6.8 branch.

Trac ticket: Core-64227


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

This new `post-branching` task is meant for any tasks that should be run immediately after creating a new numbered branch.

In addition to the pre-existing `replace:workflow-references-local-to-remote` task, a new `clean:workflows` task is being added that deletes the workflow files that are only intended for `trunk`.
@desrosj desrosj requested a review from johnbillion November 13, 2025 02:05
@desrosj desrosj self-assigned this Nov 13, 2025
@github-actions
Copy link

github-actions bot commented Nov 13, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props desrosj, johnbillion.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

desrosj added a commit to desrosj/wordpress-develop that referenced this pull request Nov 13, 2025
This runs the `post-branching` Grunt task from WordPress#10511 to test that PR.
@github-actions
Copy link

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • The Plugin and Theme Directories cannot be accessed within Playground.
  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

@desrosj
Copy link
Member Author

desrosj commented Nov 14, 2025

Waiting to merge this until the discussions on #10512 are resolved to ensure this task deletes all of the correct files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants