W3C home > Mailing lists > Public > public-test-infra@w3.org > April to June 2016

Re: Adding tools to the collection

From: Michael[tm] Smith <mike@w3.org>
Date: Sun, 24 Apr 2016 10:26:30 +0900
To: Shane McCarron <shane@spec-ops.io>
Cc: public-test-infra <public-test-infra@w3.org>
Message-ID: <20160424012630.GZ20985@sideshowbarker.net>
Hi Shane,

Shane McCarron <shane@spec-ops.io>, 2016-04-23 14:44 -0500:
> Archived-At: <http://www.w3.org/mid/CAJdbnOC305k8cHYPQCrCzv-p-ta+57Aoq-jYArL9VxQTcdfvkA@mail.gmail.com>
> 
> So - the other day I asked about Web Annotation testing via WPT and the
> consensus seemed to be that was fine.  The advice was also to add any
> "tooling" to wpt-tools.  That makes sense to me.  My question is "Is there
> a process for doing PRs that include a repository and a sub-repository?"

There isn’t, as far as I’m aware of. The process is to create forks for
each repo, and separate PRs, and in the wpt PR, just note that it depends
on PR from the wpt-tools fork.

> And on a related note, is there a document somewhere that talks about how
> to have a fork of wpt-tools integrated as a sub-module of a fork of WPT
> itself?  'cause that feels above my pay grade!

There is not, as far as I know. Of the top of my head, I guess the way it
would need to be handled is:

  1. In your wpt PR, you would need to edit the .gitmodules file to point
     to your fork of wpt-tools.

  2. After both the PRs are reviewed, the wpt-tools PR would need to be
     merged first.

  3. Finally, the wpt PR, before merging, would need to be updated to point
     to the updated canonical wpt-tools rather than your fork.

  —Mike

-- 
Michael[tm] Smith https://people.w3.org/mike

Received on Sunday, 24 April 2016 01:26:56 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 24 April 2016 01:26:56 UTC