Dealing with post-CR documents about respec-w3c-auto-publish HOT 4 CLOSED

my sense is that anything that requires manual action will be missed most of the time, so ideally, the automation tools should do their best to do the right thing.

To me, this means that the spec-prod action (great to hear about it, sounds like a fantastic idea) should adjust its operations based on the status of a spec:

• if TR spec is FPWD, republish as WD by default (without requiring a change in the echidna manifest)
• if TR spec is CR, republish as CRD by default
• if TR is PR or Rec, stop trying to republish

from respec-w3c-auto-publish.

with the new process document, this can be handled fairly easily by always publishing a CRD (which is always allowed if you've reached CR a first time). This would still need to handle the case where a doc is a PR or a Rec.

from respec-w3c-auto-publish.

Would it be possible if instead of detecting whether document can be published, users disable deployment with a flag in action.yml? There is https://github.com/sidvishnoi/spec-prod/ which allows "not deploying" (by not passing echidna token).

I plan to deprecate this action in favor of spec-prod. If manually asking not to deploy is not preferable, I can support it in spec-prod instead.

from respec-w3c-auto-publish.

Closing in favor of w3c/spec-prod#13

from respec-w3c-auto-publish.