[Questions] Github Repos can and will be taken down sometimes if they have too many forks

Mukul1127 commented 7 months ago

Have you read the FAQ?

[X] Yes, I did read the FAQ

Is there an existing issue/question for this?

[X] I have searched the existing issues

Do you think this is a bug?

❌ No, I don't think this is a bug. I will explain below

My question

Some repos like MagiskOnWSA encouraged people to fork their repo and they got shut down for how many forks they had. Just though I'd let you know

Additional context

N/A

yodaluca23 commented 7 months ago

That is true, I remember them getting shut down...

Mukul1127 commented 7 months ago

Copied from MagiskOnWsaLocal: "⚠️ 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."

yodaluca23 commented 7 months ago

What could be a solution would be to instruct people on how to unform and add a workflow to pull the latest commits from the main repo so it's not technically a fork that might have it not count against it. I'm not sure.

Mukul1127 commented 7 months ago

Better idea: Mukul1127/uYouEnhancedBuild

It seems the workflow is pretty easy to modify to just use arichorns repo so you can just create a new repo and create the build file.

Mukul1127 commented 7 months ago

Misread your comment but same idea

Mukul1127 commented 7 months ago

Fixed action but libcolorpicker is failing to link:

==> Linking library libcolorpicker (arm64)…
clang: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[5]: *** [/Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/theos/makefiles/instance/library.mk:52: /Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/main/.theos/obj/arm64/libcolorpicker.dylib] Error 1
gmake[4]: *** [/Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/theos/makefiles/instance/library.mk:52: /Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/main/.theos/obj/arm64/libcolorpicker.dylib] Error 2
gmake[3]: *** [/Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/theos/makefiles/instance/library.mk:[37](https://github.com/Mukul1127/uYouEnhancedBuild/actions/runs/8527511438/job/23359099293#step:10:38): internal-library-all_] Error 2
gmake[2]: *** [/Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/theos/makefiles/master/rules.mk:146: libcolorpicker.all.library.variables] Error 2
gmake[1]: *** [/Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/theos/makefiles/master/aggregate.mk:12: internal-all] Error 2
gmake: *** [/Users/runner/work/uYouEnhancedBuild/uYouEnhancedBuild/theos/makefiles/master/aggregate.mk:12: internal-all] Error 2
Error: Process completed with exit code 2.

jianmingyong commented 7 months ago

I guess if the people manually create a new repo by pulling the latest commit here and not use the fork button, it will not count towards it since there is no linkage to the main repo.

Basically time to learn some basic git commands.

Clone this repo, add a new remote to your new clean repo. Push it there and then run the actions. Since it is your own repo without fork, that is relatively safe.

bhackel commented 7 months ago

Does the import feature: https://github.com/new/import also cause problems with having too many clones of a repo?

Mukul1127 commented 7 months ago

Maybe but it's dying in a week

bhackel commented 7 months ago

I think thats just for subversion and some other stuff - regardless, I think that repo takedown is done manually and there isn't a great way to get around it, since we are relying on github actions for building.

Mukul1127 commented 7 months ago

The actions script can be edited to just pull the main repo, I did it in a seperate repo here: https://github.com/Mukul1127/uYouEnhancedBuild

just did this:

      - uses: actions/checkout@v4.1.1
        with:
          repository: arichornlover/uYouEnhanced

Mukul1127 commented 7 months ago

I think thats just for subversion and some other stuff - regardless, I think that repo takedown is done manually and there isn't a great way to get around it, since we are relying on github actions for building.

Seems to work after enabling actions in settings

arichornlover / uYouEnhanced