Jon Koops
Jon Koops
After reading the linked documentation I don't understand how this should resolve this issue. From what I can tell it specifies that forks should have their own secrets? That doesn't...
1. These are all public forks. 2. My problem is that putting it in a secret makes said secret unavailable to forks (this is just how Github secrets work).
> If they are public forks then the record key needs to be set as a secret separately for each fork. That was the original problem that I wanted to...
I have, but our entire team works from forks so that would essentially make the Cypress Cloud useless for our current workflow.
> I don't know how this could be solved, but perhaps a Cypress Cloud project could be configured so that it only accepts input from a certain repository and forks...
Thanks for getting back to me on that @nagash77. So it seems we can not really use Cypress Cloud securely with our current workflow, that is unfortunate, but at least...
Please [sign off on your commit](https://github.com/keycloak/keycloak-nodejs-connect/pull/515/checks?check_run_id=22868526206)
I think we could parse the URL of the tile-server in general and match it against a couple of known domains: ```js const url = new URL('https://tile.openstreetmap.org/{z}/{x}/{y}.png'); const osmHosts =...
+1 let's throw this in the bin.
To get back to the discussion under #9316. > My use case, as a consumer, is that I love being able to install a package and not have to think...