[wp-trac] [WordPress Trac] #57556: Configure feature branches on GitHub to trigger workflows to support development on forks

[WordPress Trac]

#57556: Configure feature branches on GitHub to trigger workflows to support
development on forks
----------------------------------+------------------------------
 Reporter:  flixos90              |       Owner:  (none)
     Type:  enhancement           |      Status:  new
 Priority:  normal                |   Milestone:  Awaiting Review
Component:  Build/Test Tools      |     Version:
 Severity:  normal                |  Resolution:
 Keywords:  has-patch needs-docs  |     Focuses:
----------------------------------+------------------------------

Comment (by flixos90):

 @jorbin @peterwilsoncc Given the additional context you provided, I agree
 we would want to verify intent to run the CI workflows. I think a branch
 name prefix like `wp-pipeline/*` works well for that purpose. I think
 including a specific file does not work so well as it would need to be
 created per branch, and then it would also inevitably show up in the
 eventual PRs against `WordPress/wordpress-develop` - unless it was
 deleted, but then also CI workflows would stop running for PRs in the
 fork. So I think a specific branch name prefix works better.

 > Adding the needs docs keyword since this is something that we will want
 to communicate in both a short-term sense on make/core but also in a long-
 term sense by making either a handbook update or perhaps also a
 CONTRIBUTING.md update.

 I am happy to draft some documentation for that. Related question though,
 is there any documentation on how this currently works? Where is it
 documented that fork PRs against `trunk` trigger GitHub workflows for
 example?

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/57556#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform