Skip to content

Scripts: Remove obsolete bin/setup-local-env.sh#78871

Merged
manzoorwanijk merged 1 commit into
trunkfrom
remove/obsolete-setup-local-env
Jun 2, 2026
Merged

Scripts: Remove obsolete bin/setup-local-env.sh#78871
manzoorwanijk merged 1 commit into
trunkfrom
remove/obsolete-setup-local-env

Conversation

@manzoorwanijk

@manzoorwanijk manzoorwanijk commented Jun 2, 2026

Copy link
Copy Markdown
Member

What?

Removes the obsolete bin/setup-local-env.sh script. It's a part of the clean up of the bin/ directory in #75041.

Why?

This script was retired roughly 7 years ago in #17004 ("Switch to using the Core local environment"), when the project moved to wp-env / the Core local environment. Since then its only content has been a notice telling users it has been retired and to run npm run wp-env start instead.

Nothing in the codebase references the script anymore (no package.json scripts, docs, or other tooling point to it), so the stub serves no purpose and can be safely removed.

How?

Deletes bin/setup-local-env.sh. No other files reference it, so no further changes are needed.

Testing Instructions

  1. Confirm bin/setup-local-env.sh no longer exists.
  2. Run git grep setup-local-env and verify there are no remaining references.
  3. Verify the documented local-environment workflow is unaffected: npm run wp-env start still sets up a local environment as expected.

Testing Instructions for Keyboard

N/A — no user interface changes.

Screenshots or screencast

N/A

Use of AI Tools

This pull request was authored with the assistance of Claude Code. All changes were reviewed by the author.

@github-actions

github-actions Bot commented Jun 2, 2026

Copy link
Copy Markdown

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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: t-hamano <wildworks@git.wordpress.org>

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

@manzoorwanijk manzoorwanijk self-assigned this Jun 2, 2026
@manzoorwanijk manzoorwanijk added the [Type] Code Quality Issues or PRs that relate to code quality label Jun 2, 2026
The script was retired ~7 years ago in #17004 when the project moved to
the Core local environment (wp-env). Since then it only printed a notice
telling users it had been retired. Nothing in the codebase references it,
so the stub can be safely removed.
@manzoorwanijk manzoorwanijk force-pushed the remove/obsolete-setup-local-env branch from 1ccaa9e to 4b112c0 Compare June 2, 2026 08:49

@t-hamano t-hamano left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Surely, this warning is no longer necessary.

@manzoorwanijk manzoorwanijk merged commit 8856ab3 into trunk Jun 2, 2026
47 of 48 checks passed
@manzoorwanijk manzoorwanijk deleted the remove/obsolete-setup-local-env branch June 2, 2026 09:43
@github-actions github-actions Bot added this to the Gutenberg 23.4 milestone Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Type] Code Quality Issues or PRs that relate to code quality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants