search

WICG / private-network-access

https://wicg.github.io/private-network-access/
Other
57 stars 22 forks source link

Fix some typos. #65

Closed miketaylr closed 2 years ago

miketaylr commented 2 years ago

ipr — The repository manager doesn't know the following repository: WICG/private-network-access

y tho

miketaylr commented 2 years ago

PTAL @letitz

mikewest commented 2 years ago

This PR is purely editorial, so I'm going to land it despite the failing check, but /cc @yoavweiss for the IPR check.

yoavweiss commented 2 years ago

Agree that this is not substantive. I also think @miketaylr is already a WICG member, so the main question is why are the bots borked..

miketaylr commented 2 years ago

I also think @miketaylr is already a WICG member, so the main question is why are the bots borked..

Yep, I'm a WICG member. Also publishing seems to be busted (assuming it's automated), https://wicg.github.io/private-network-access/ is still showing June 23rd. 🤷

letitz commented 2 years ago

@yoavweiss halp! I don't know why the bots are borked. Where can I find out more?

yoavweiss commented 2 years ago

@yoavweiss halp! I don't know why the bots are borked. Where can I find out more?

Is this happening on other PRs as well?

letitz commented 2 years ago

Not that I know of, but there has been no other PR affecting the spec text since June 23rd. Would it help if I tried to merge a quick PR as a test?

yoavweiss commented 2 years ago

Yeah, that can help figure out if this is a one off or a persistent issue

letitz commented 2 years ago

Oh! Oh. :facepalm:

The problem is not busted bots. The problem is that make was not run so index.html was not updated to reflect index.src.html. Sorry for the noise. I'll fix it.

letitz commented 2 years ago

Pushed 497ee7ec6cfddb8b5e572a8cfed4bcb8abeeb226.