Make WordPress Core


Ignore:
Timestamp:
07/02/2026 06:03:43 PM (4 months ago)
Author:
desrosj
Message:

Build/Test Tools: Disable welcome messages for pull requests.

In [62486], the logic responsible for posting a welcome message to new contributors was changed to use the actions/first-interaction action. Since then, a welcome message has been posted on every new pull request.

The behavior seems to be caused by the fact that issues are disabled for the wordpress-develop repository, which causes the action to consider every new PR from a new contributor.

This removes the welcome message until the bug can be fixed upstream or a new solution can be created.

Props westonruter, johnbillion, wildworks, desrosj.
See #65432.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/.github/workflows/pull-request-comments.yml

    r62490 r62629  
    2121
    2222jobs:
    23   # Comments on a pull request when the author is a first time contributor.
    24   post-welcome-message:
    25     runs-on: ubuntu-24.04
    26     permissions:
    27       issues: write
    28       pull-requests: write
    29     timeout-minutes: 5
    30     if: ${{ github.repository == 'WordPress/wordpress-develop' && github.event_name == 'pull_request_target' }}
    31     steps:
    32       - name: Post a welcome comment
    33         uses: actions/first-interaction@1c4688942c71f71d4f5502a26ea67c331730fa4d # v3.1.0
    34         with:
    35           # While issues are disabled for this repository and this will not post anywhere, this action configures both
    36           # message inputs as required.
    37           # See https://github.com/actions/first-interaction/issues/365.
    38           issue_message: |
    39             "Baseball is dull only to dull minds." - Red Barber
    40           pr_message: >
    41             Hi there! 👋
    42 
    43 
    44             Thank you for your contribution to WordPress! 💖
    45 
    46 
    47             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!
    48 
    49 
    50             **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.
    51 
    52 
    53             **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.
    54 
    55 
    56             More information about how GitHub pull requests can be used to contribute to WordPress can be found in [the Core Handbook](https://make.wordpress.org/core/handbook/contribute/git/github-pull-requests-for-code-review/).
    57 
    58 
    59             **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.
    60 
    61 
    62             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/).
    63 
    64 
    65             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:
    66 
    67             - [PHP Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/php/)
    68 
    69             - [CSS Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/css/)
    70 
    71             - [HTML Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/html/)
    72 
    73             - [JavaScript Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/javascript/)
    74 
    75             - [Accessibility Coding Standards](https://developer.wordpress.org/coding-standards/wordpress-coding-standards/accessibility/)
    76 
    77             - [Inline Documentation Standards](https://developer.wordpress.org/coding-standards/inline-documentation-standards/)
    78 
    79 
    80             Thank you,
    81 
    82             The WordPress Project
    83 
    8423  # Leaves a comment on a pull request with a link to test the changes in a WordPress Playground instance.
    8524  playground-details:
Note: See TracChangeset for help on using the changeset viewer.