-
Notifications
You must be signed in to change notification settings - Fork 167
Fix #2281: CR 2020-12-15 #2283
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
Fix #2281: CR 2020-12-15 #2283
Conversation
Create a new CR for 2020-12
Well, that was unexpected. Travis fails but when I run bikeshed locally updated just now (like our Travis CI), I get no issues. |
@svgeesus Can you check that I made the right changes for CR? I'll have to figure out why Travis isn't like this, but maybe it doesn't matter as long as I can build it locally myself. The preview looks ok. |
Of course, this MUST NOT be merged to the main branch, since that's for the editor's branch. |
Ok great, this is good to build now. Then I can do the pubrules check and broken link check. |
Link to implementation-report.html for the required Implementation Report metadata for CR.
Bikeshed complains about some ambiguous links so set the link-defaults to one of the links bikeshed suggests. We generally prefer the HTML version if available. The updated links are for - Promise - Worklet - worklet global scope type - worklet destination type - addModule - WorkletGlobalScope
I think we're all set now. bikeshed doesn't produce any new errors now. |
The actual candidate recommendation happened on a different date. Update them to match the actual date of publication.
Create a new CR for 2020-12
Preview | Diff