-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add auto-publish script #171
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A couple changes in order to avoid having two deploy scripts:
Co-authored-by: Jeffrey Yasskin <[email protected]>
Co-authored-by: Jeffrey Yasskin <[email protected]>
Co-authored-by: Jeffrey Yasskin <[email protected]>
Can this be merged? |
This looks good to me. If it looks good to @hober too then i'm good with merging |
Privacy Working Group discussed and agreed on this: https://github.com/w3c/privacywg/blob/main/minutes/privacywg-20241121.md#a-securityprivacy-questionnaire |
SHA: c5ffa65 Reason: push, by pes10k Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
SHA: c5ffa65 Reason: push, by pull[bot] Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
The SoTD produced by that script has a different licensing requirement section, I don't think there is an issue now, but it was some times ago. If no-one complains about it, I can only be happy that auto-publishing is working now! |
SHA: c5ffa65 Reason: push, by plehegar Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Ideally, we should point to a link where TAG and PING are agreeing to do this. Having said that, this pull request could serve as such.
@torgo @plinss @npdoty @pes10k