sergiotarxz/Wordpress
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
f586f9d799
Wordpress/.github/workflows/welcome-new-contributors.yml

61 lines
2.8 KiB
YAML
Raw Normal View History

Build/Test Tools: Introduce GitHub Action workflows. This change introduces 6 different workflows accounting for all of the testing and analysis currently performed in Travis CI & Appveyor: - Checking PHP & JS coding standards are followed - Running the end-to-end test suite. - Running QUnit tests on JavaScript files. - Scanning for PHP compatibility issues with supported version. - Running the PHPUnit test suite. - Verifying NPM related tasks do not cause errors on Windows. Additionally, a seventh workflow is included that will leave a "welcome" comment when a contributor opens their first pull request to the `wordpress-develop` mirror. These workflows are currently in an experimental phase. For that reason, Travis CI and Appveyor will continue to run until all of the bugs can be worked out. Props ayeshrajans, helen, ocean90, desrosj. See #50401. git-svn-id: https://develop.svn.wordpress.org/trunk@49162 602fd350-edb4-49c9-b593-d223f7449a82
2020-10-15 21:40:33 +02:00
name: Welcome New Contributors
on:
Build/Test Tools: Change the event that triggers the “Welcome” workflow. When a contributor opens their first pull request to `wordpress-develop`, the “Welcome” workflow runs and leaves a comment with guidance, helpful information, and resources. However, because a workflow run triggered by the `pull_request` event runs against the workflow and code from the merge commit, the needed context and permissions to comment on the pull request are missing. By changing the trigger event to `pull_request_target`, the workflow runs against the workflow and code in the base of the pull request and is able to comment on when appropriate. See #50401. git-svn-id: https://develop.svn.wordpress.org/trunk@49169 602fd350-edb4-49c9-b593-d223f7449a82
2020-10-16 02:37:03 +02:00
pull_request_target:
Build/Test Tools: Introduce GitHub Action workflows. This change introduces 6 different workflows accounting for all of the testing and analysis currently performed in Travis CI & Appveyor: - Checking PHP & JS coding standards are followed - Running the end-to-end test suite. - Running QUnit tests on JavaScript files. - Scanning for PHP compatibility issues with supported version. - Running the PHPUnit test suite. - Verifying NPM related tasks do not cause errors on Windows. Additionally, a seventh workflow is included that will leave a "welcome" comment when a contributor opens their first pull request to the `wordpress-develop` mirror. These workflows are currently in an experimental phase. For that reason, Travis CI and Appveyor will continue to run until all of the bugs can be worked out. Props ayeshrajans, helen, ocean90, desrosj. See #50401. git-svn-id: https://develop.svn.wordpress.org/trunk@49162 602fd350-edb4-49c9-b593-d223f7449a82
2020-10-15 21:40:33 +02:00
types: [ opened ]
jobs:
post-welcome-message:
runs-on: ubuntu-latest
steps:
- uses: bubkoo/welcome-action@v1
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
FIRST_PR_COMMENT: >
Hi @{{ author }}! 👋
Thank you for your contribution to WordPress! 💖
It looks like this is your first pull request, so 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 one mirrors. But please feel free to use 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/).
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/)
Please remember that the WordPress project is largely maintained by volunteers
Thank you,
The WordPress Project
Reference in New Issue Copy Permalink