Update generated support links#292
Conversation
|
Hello! 👋 Thanks for opening this pull request! Please check out our contributing guidelines. We appreciate you taking the initiative to contribute to this project. Contributing isn't limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation. Here are some useful Composer commands to get you started:
To run a single Behat test, you can use the following command: # Run all tests in a single file
composer behat features/some-feature.feature
# Run only a specific scenario (where 123 is the line number of the "Scenario:" title)
composer behat features/some-feature.feature:123You can find a list of all available Behat steps in our handbook. |
|
In this section we actually used to link to a bunch of resources, including Slack. See https://web.archive.org/web/20260403123630/https://wp-cli.org/ We should add a new Support section to https://make.wordpress.org/cli/handbook/ with similar content and link to that instead. This can be contributed via a PR at https://github.com/wp-cli/handbook/ |
|
Thanks for the guidance. I opened wp-cli/handbook#645 to add a dedicated Support page with the support resources from the archived wp-cli.org page. Once that is reviewed, I can update this PR to point the generated support link to the new handbook page. |
Summary
Updates the support link used in generated package files.
The old
wp-cli.org/#supportlink now redirects to the general WordPress.org CLI page, so this points people to the WP-CLI common issues guide instead.Changes
Verification
composer lint.composer phpcs.composer phpstan.