[ci] Disable workflows with secrets and custom runners to run on fork
Author: HollowMan6
Pull request: yes

# What does this PR do?

<!--
Congratulations! You've made it this far! You're not quite done yet though.

Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution.

Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change.

Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost.
-->

<!-- Remove if not applicable -->

Skip those workflows by checking if the repository is owned by `huggingface`.

Tested by directly pushing to the fork: https://github.com/HollowMan6/transformers/commit/14be7f3c250c3ba1887877fc1df67b2e87559759

and opening a PR on the fork side:
- https://github.com/HollowMan6/transformers/pull/1

## Before submitting
- [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
- [X] Did you read the [contributor guideline](https://github.com/huggingface/transformers/blob/main/CONTRIBUTING.md#create-a-pull-request),
      Pull Request section?
- [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link
      to it if that's the case.
- [ ] Did you make sure to update the documentation with your changes? Here are the
      [documentation guidelines](https://github.com/huggingface/transformers/tree/main/docs), and
      [here are tips on formatting docstrings](https://github.com/huggingface/transformers/tree/main/docs#writing-source-documentation).
- [ ] Did you write any new necessary tests?


## Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

<!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @

 If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**.
 Please tag fewer than 3 people.

Models:

- text models: @ArthurZucker @Cyrilvallez
- vision models: @yonigozlan @molbap
- audio models: @eustlb @ebezzam @vasqu
- multimodal models: @zucchini-nlp
- graph models: @clefourrier

Library:

- generate: @zucchini-nlp (visual-language models) or @gante (all others)
- continuous batching: @remi-or @ArthurZucker @McPatate
- pipelines: @Rocketknight1
- tokenizers: @ArthurZucker and @itazap
- trainer: @zach-huggingface @SunMarc
- attention: @vasqu @ArthurZucker @CyrilVallez
- model loading (from pretrained, etc): @CyrilVallez
- distributed: @3outeille @ArthurZucker @S1ro1
- CIs: @ydshieh

Integrations:

- deepspeed: HF Trainer/Accelerate: @SunMarc @zach-huggingface
- ray/raytune: @richardliaw, @amogkam
- Big Model Inference: @SunMarc
- quantization (bitsandbytes, autogpt): @SunMarc @MekkCyber
- kernels: @MekkCyber @drbh
- peft: @BenjaminBossan @githubnemo

Devices/Backends:

- AMD ROCm: @ivarflakstad
- Intel XPU: @IlyasMoutawwakil
- Ascend NPU: @ivarflakstad 

Documentation: @stevhliu

Research projects are not maintained and should be taken as is.

 -->

@ydshieh


Comments:
I feel like we're probably not leaking secrets to everyone who forks the repo, so I'm not sure if this is necessary! cc @ydshieh to confirm

I feel like it would be preferable to exclude those CIs that can't run in a fork, otherwise it's quite annoying to get those floods of error messages from GitHub if we modify something in the fork while we still want some CI to be working.

Ah, that's a good point, sorry! I misread this as being about protecting secrets rather than improving the CI in forks

Yes, secret won't be leaked but triggered on forked repo is annoying.

Let me think if this PR is the best approach ...

Thank you for opening.

<img width="2477" height="787" alt="Screenshot 2025-10-16 163008" src="https://github.com/user-attachments/assets/0d54b518-2a94-4285-a183-c59420371fa3" />

Maybe it's better to do this 🙏 

putting the condition in many jobs doesn't really seem a very good / reliable approach to me.



Okay, yeah, I was meant to still get some CI working when we modify something in the fork. Now I double checked the CI and saw that almost all the CIs are disabled now... So this might not be necessary at all, and it's better to disable the GitHub Actions completely.

Thanks for your feedback anyway. Closing this PR.