3 ms·
I'm curious to see how this changes over time, so I threw together a quick repo with a GitHub action to watch the endpoint. https://github.com/b0o/apple-autofi
by HellsMaddy 5y ago
I'm curious to see how this changes over time, so I threw together a quick repo with a GitHub action to watch the endpoint.
https://github.com/b0o/apple-autofill-domains https://github.com/b0o/apple-autofill-domains
- nly 5y agoMy bet is it's a manual update process once in a blue moon
- hiccuphippo 5y agoInteresting! Perhaps it could even post a comment to an issue so people can subscribe to it.
- HellsMaddy 5y agoGood idea! I’ve created an issue[0] that can be subscribed to, I will implement the feature soon. [0]: https://github.com/b0o/apple-autofill-domains/issues/1 https://github.com/b0o/apple-autofill-domains/issues/1
- asah 5y agoRandom q: why fetch depth 20?
- HellsMaddy 5y agoThat’s actually a bug, thank you. It will break as soon as the last modification to the data file is more than 20 commits behind HEAD. I used 20 because it made the workflow function (it was working on my local machine but not when I pushed to GitHub because the default depth is 1). I need to update it to check for the last commit that modified the json file rather than searching through the entire commit history.
- jzelinskie 5y agoYou should be careful with the cron intervals because GitHub eventually just disabled one of the actions that I wrote that worked exactly like this. I was generating a list of the YouTube's dynamic ad-serving domains.