Skip to content
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

建议每月发布一个release,而不是github actions #4

Closed
SekiBetu opened this issue Aug 14, 2022 · 6 comments
Closed

建议每月发布一个release,而不是github actions #4

SekiBetu opened this issue Aug 14, 2022 · 6 comments

Comments

@SekiBetu
Copy link
Contributor

建议每月发布一个release,而不是github actions,这样原仓库应该就没问题了

@Howard20181
Copy link
Member

不知道会不会有版权问题
而且发布Release之后下载量大也不行,之前OpenGapps就迁移了

@SekiBetu
Copy link
Contributor Author

SekiBetu commented Aug 14, 2022

那没办法了,十万个fork,经常build,把微软服务器干趴下了属于是,要么release放在谷歌盘之类的地方吧,没有版权问题的吧,WSA内核是开源的吧

@Howard20181
Copy link
Member

现在Github没有回应是什么原因禁用

@Howard20181 Howard20181 closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2022
@PeterNjeim
Copy link

PeterNjeim commented Aug 17, 2022

I don't like it when companies don't specify what term of the ToS was violated, it's not transparent. But of course, we all know that the old repository abused GitHub Actions, and even I called you guys out on that, and released my own fork that used Releases instead of Actions (mainly because it's way faster (47x faster) and more reliable anyways). Unfortunately, since it was a fork, my repository got disabled as well. I am now in contact with GitHub to reinstate my repository. If they do, then I will report back here and confirm that it wasn't a copyright issue. If they deny my request, then we can safely say that it would be a copyright issue and that this local method is the correct way forward.

torlmen pushed a commit to torlmen/MagiskOnWSALocal that referenced this issue Aug 23, 2022
@PeterNjeim
Copy link

@Howard20181
They replied to me, it is confirmed an Actions issue. If you use Releases like I did I'm sure it wouldn't violate their policies.

image

@PeterNjeim
Copy link

PeterNjeim commented Jan 9, 2023

@Howard20181 My repository just got banned just like your old one lol. I'm contacting them right now to see if Releases are also a problem, or if it's a copyright issue.

Update: it was banned for the exact same reason as your old one (picture in my previous comment). Literally the same two points. However the final sentence was different. Instead of mentioning an undue burden through the use of Actions, they said that it was due to the "nature and volume of the prohibited activity".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
@PeterNjeim @SekiBetu @Howard20181 and others