Fixed missng url escaping #4426
Workflow file for this run
This file contains 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
| name: Welcome New Contributors | |
| on: | |
| pull_request_target: | |
| types: [ opened ] | |
| # Disable permissions for all available scopes by default. | |
| # Any needed permissions should be configured at the job level. | |
| permissions: {} | |
| jobs: | |
| # Comments on a pull request when the author is a new contributor. | |
| post-welcome-message: | |
| runs-on: ubuntu-latest | |
| permissions: | |
| issues: write | |
| timeout-minutes: 5 | |
| if: ${{ github.repository == 'WordPress/wordpress-develop' }} | |
| steps: | |
| - uses: wow-actions/welcome@72817eb31cda1de60f51893d80e2e82ce57f7e76 # v1.3.0 | |
| with: | |
| FIRST_PR_COMMENT: > | |
| Hi @{{ author }}! 👋 | |
| Thank you for your contribution to WordPress! 💖 | |
| It looks like this is your first pull request to `wordpress-develop`. Here are a few things to be aware of that may help you out! | |
| **No one monitors this repository for new pull requests.** Pull requests **must** be attached to a Trac ticket to be considered for inclusion in WordPress Core. To attach a pull request to a Trac ticket, please include the ticket's full URL in your pull request description. | |
| **Pull requests are never merged on GitHub.** The WordPress codebase continues to be managed through the SVN repository that this GitHub repository mirrors. Please feel free to open pull requests to work on any contribution you are making. | |
| More information about how GitHub pull requests can be used to contribute to WordPress can be found in [this blog post](https://make.wordpress.org/core/2020/02/21/working-on-trac-tickets-using-github-pull-requests/). | |
| **Please include automated tests.** Including tests in your pull request is one way to help your patch be considered faster. To learn about WordPress' test suites, visit the [Automated Testing](https://make.wordpress.org/core/handbook/testing/automated-testing/) page in the handbook. | |
| If you have not had a chance, please review the [Contribute with Code page](https://make.wordpress.org/core/handbook/contribute/) in the [WordPress Core Handbook](https://make.wordpress.org/core/handbook/). | |
| The [Developer Hub](https://developer.wordpress.org/) also documents the various [coding standards](https://make.wordpress.org/core/handbook/best-practices/coding-standards/) that are followed: | |
| - [PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/) | |
| - [CSS Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/css/) | |
| - [HTML Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/) | |
| - [JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/) | |
| - [Accessibility Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/) | |
| - [Inline Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/) | |
| Thank you, | |
| The WordPress Project |