search

w3c / rdf-schema

https://w3c.github.io/rdf-schema/
Other
5 stars 1 forks source link

Update `spec/common/participants.html` file #6

Closed timothee-haudebourg closed 1 year ago

timothee-haudebourg commented 1 year ago

There is still an issue with my name in this file. @gkellogg I could re-generate it, but wouldn't it be better to have common be a submodule used by all the RDF 1.2 repositories?

gkellogg commented 1 year ago

We tried sub-modules, but it is incompatible with PR Preview and other build processes, so we had to back off. This means that when creating a new PR after rdf-common is updated, the contents need to be synchronized manually.

gkellogg commented 1 year ago

I updated in PR #5.

TallTed commented 1 year ago

@gkellogg

the contents need to be synchronized manually

I wonder whether a GitHub Action could be used to automate this sync? (I know GitHub Actions exist and seem like they should work for this, but I know virtually nothing about using them, so I cannot provide more details on this thought.)

Tpt commented 1 year ago

I wonder whether a GitHub Action could be used to automate this sync? (I know GitHub Actions exist and seem like they should work for this, but I know virtually nothing about using them, so I cannot provide more details on this thought.)

It should definitely be possible if a W3G GitHub organization admin is ok to create an access token to all RDF and SPARQL repositories. Thee the doc.

gkellogg commented 1 year ago

It is possible, and I’m working on something similar for RCH, but haven’t gotten there yet. It will require coordination on repo settings. The current action that checks for consistency could potentially be updated to commit changed files, instead.