[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:
----------------------------------+------------------------------
Changes (by jorbin):

 * keywords:  has-patch => has-patch needs-docs


Comment:

 I think the reasons that @peterwilsoncc mentions are valid, but I think we
 can get around them with some documentation and making it specific to a
 naming convention.  I worry that `feature/*` is too generic though. Maybe
 we make it something WP specific? `wp-pipeline/*` perhaps to indicate that
 this is change that should trigger WordPress pipeline actions?

 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.

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