[CI] Continuous spam of PyTorch CI build status notifications in fork

Open
#138,564 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
24/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
github-actions
Domain
ci-cd

Research direction

The issue names no files, tests, or entry points. Start by reviewing the repository's CI configuration and the GitHub fork's build-status notification behavior; done means relevant changes still produce status notifications without sending repeated notifications for unrelated fork activity.

Written by the indexing model from the issue text.

Description

actionable module: ci triaged

Ever since forking the PyTorch repo, in just a month I have received over 200+ notifications from the CI build status. Such notifications should only be triggered for the specific changes the author made (say when opening a PR) just like other repos.

GitHub's global CI notifications option turns off all, so that isn't quite the solution.

cc @seemethere @malfet @pytorch/pytorch-dev-infra

Dominant language
Python
Stars
103k
Forks
29.9k
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pytorch/pytorch

All issues in pytorch/pytorch

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.