[wp-meta] [Making WordPress.org] #2981: Proper destination for codebase logging WP PHPUnit test run results?
Making WordPress.org
noreply at wordpress.org
Thu Jul 27 21:38:17 UTC 2017
#2981: Proper destination for codebase logging WP PHPUnit test run results?
-----------------------------+------------------
Reporter: danielbachhuber | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: General | Resolution:
Keywords: |
-----------------------------+------------------
Comment (by danielbachhuber):
Replying to [comment:3 pento]:
> - The server repo definitely needs to be moved to the WordPress GitHub
org, and I think the client repo probably should be, too.
I agree. What's the best way to go about this? If we add you as an admin
on the repos, can you transfer them in and then create a team for us to
manage contributors?
> - I think o2 is fine with custom post types (see the handbook, for
example), but it might be a bit quirky. Be prepared.
Lovely :)
> - I'm not wild about the server using `edit_posts` as the auth
capability. A custom capability would be better, so that hosts can link it
to a host-controlled w.org account, that just needs to be a user on
make/hosting.
Good suggestion, we'll take care of it.
> Finally, it looks like the server front end is being built as a theme?
Is that still the plan, or will it be a plugin, instead? I think I'd
prefer a plugin, that'd be easier to integrate with w.org's existing UI.
We're doing a bit of refactoring at the moment. The high-level overview to
the refactor is here: https://paper.dropbox.com/doc/WP-Unit-Test-Reporter-
tssvu4ACKCQPcY3jHnaiX
tl;dr: Yes, it will just be a plugin.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2981#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list