meta-pytorch / meta-pytorch/data
Disable cron job running on forked repo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 179
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 2
Description
🐛 Describe the bug
My forked repo of torchdata have been running the cron job to validate nightly binaries.
See workflow https://github.com/ejguan/data/actions/runs/4097726223
@atalman Is this expected? Can we disable it by doing something like:
https://github.com/pytorch/data/blob/01fc76200354501b057bb439b43a1f05f609dd0a/.github/workflows/nightly_release.yml#L11
Versions
main
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with .github/workflows/nightly_release.yml, especially the referenced condition near line 11, and compare its behavior in the upstream and forked repositories. Confirm that the nightly binary-validation workflow does not run for forks, while retaining the intended behavior in the main repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100