Do not run CI on forked repos

[janeyx99]

Context

What is the purpose of this PR? Is it to

• add a new feature
• fix a bug
• update tests and/or documentation
• other (please add here)

Please link to any issues this PR addresses.

https:/janeyx99/torchtune/actions/runs/11004925000 Every night I get 2 spammy emails telling me my CI doesn't work, but like duh it doesn't work on my fork. Thanks @felipemello1 for explaining the problem, and here's the PR to gate CI behind this repo!

FYI this experience is not very fun for OSS contributors because CI will run on their forks, and they will either get errors, or compute will be wasted on running the periodic CI.

Changelog

What are the changes made in this PR?

• Mentioned above

Test plan

Please make sure to do each of the following if applicable to your PR. If you're unsure about any one of these just ask and we will happily help. We also have a contributing page for some guidance on contributing.

• run pre-commit hooks and linters (make sure you've first installed via pre-commit install)
• add unit tests for any new functionality
• update docstrings for any new or updated methods or classes
• run unit tests via pytest tests
• run recipe tests via pytest tests -m integration_test
• manually run any new or modified recipes with sufficient proof of correctness
• include relevant commands and any other artifacts in this summary (pastes of loss curves, eval results, etc.)

UX

If your function changed a public API, please add a dummy example of what the user experience will look like when calling it.
Here is a docstring example
and a tutorial example

• I did not change any public API
• I have added an example to docs or docstrings

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/torchtune/1681

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit b2d1a37 with merge base 7eb362c ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[felipemello1]

Thanks, @janeyx99! You are a champ! Do you know the best way to test it? Just let the CI run?

[janeyx99]

@felipemello1 Yes, nothing should be changed in torchtune CI (and I should stop getting emails).

[ebsmothers]

This is why I was getting all those emails?! Seriously though.. thank you for fixing this

[ebsmothers]

I'm curious about this one in particular.. why isn't github.repository == 'pytorch/torchtune' sufficient? My assumption is that forks would have a separate repository name, is that not the case?

[janeyx99]

it totally was sufficient, i just changed it for consistency so someone looking can see that it’s the same across the workflows