3 ms·
I was reading the linked repo in step 2 <https://github.com/LSPosed/MagiskOnWSALocal#magisk-on-wsa-with-google-apps https://github.com/LSPosed/MagiskOnWSALocal#
by mdaniel 4y ago
I was reading the linked repo in step 2 <https://github.com/LSPosed/MagiskOnWSALocal#magisk-on-wsa-with-google-apps https://github.com/LSPosed/MagiskOnWSALocal#magisk-on-wsa-wi...> and saw this message, which seems like utter nonsense:
> For fork developers: Please don't build using GitHub Actions, as GitHub will count your forked GitHub Actions usage against this upstream repository, which may cause this upstream repository gets disabled by GitHub staff like MagiskOnWSA because of numerous forks building GitHub Actions, and counting the forks' Action usage against this upstream repository.
is that even remotely true?
If there's any "disabled by GitHub staff" going on, it's likely due to DMCA nonsense, not due to forks having their GitHub Actions billed against the upstream repo. Related to that, I'm surprised to see the submitted repo distribute icu.dll and winhttp.dll, versus telling interested parties to extract them out of the Win11 ISO. I bet Microsoft won't bother striking the repo over 2 random dlls but why roll the dice?
- LiamPowell 4y agoRather than hosting the build artifacts, MagiskOnWSA asked users to fork the repo and run a GitHub action to build a 2GB file. Given that they had over 100,000 forks (or at least 200TB of identical artifacts), it's pretty clear why GitHub disabled their repo.