From 59fddb00f2ba17ae57f083a615762087f68af29d Mon Sep 17 00:00:00 2001 From: William Lin Date: Wed, 14 Oct 2026 23:40:45 -0700 Subject: [PATCH] [ci] Remove automated community comments (#1962) --- .github/mergify.yml | 74 ------------------------- .github/workflows/community-stale.yml | 17 ------ .github/workflows/community-welcome.yml | 56 ------------------- docs/contributing/ci_architecture.md | 8 ++- 4 files changed, 6 insertions(+), 149 deletions(-) delete mode 100644 .github/workflows/community-welcome.yml diff --git a/.github/mergify.yml b/.github/mergify.yml index 65318a44b..27b43363c 100644 --- a/.github/mergify.yml +++ b/.github/mergify.yml @@ -205,40 +205,6 @@ pull_request_rules: label: add: ["scope: model"] - # ============================================================ - # Pre-commit failure help comment - # ============================================================ - - - name: comment on pre-commit failure - conditions: - - check-failure~=pre-commit - - -closed - actions: - comment: - message: | - ## Pre-commit checks failed - - Hi @{{author}}, the pre-commit checks have failed. To fix them locally: - - ```bash - # Install pre-commit if you haven't already - uv pip install pre-commit - pre-commit install - - # Run all checks and auto-fix what's possible - pre-commit run --all-files - ``` - - Common fixes: - - **yapf**: `yapf -i ` (formatting) - - **ruff**: `ruff check --fix ` (linting) - - **codespell**: `codespell --write-changes ` (spelling) - - After fixing, commit and push the changes. The checks will re-run automatically. - - For future commits, `pre-commit` will run automatically on changed files before each commit. - - # ============================================================ # Merge conflict detection # ============================================================ @@ -251,16 +217,6 @@ pull_request_rules: actions: label: add: [needs-rebase] - comment: - message: | - This PR has merge conflicts with the base branch. Please rebase: - - ```bash - git fetch origin main - git rebase origin/main - # Resolve any conflicts, then: - git push --force-with-lease - ``` - name: remove conflict label when resolved conditions: @@ -290,35 +246,5 @@ pull_request_rules: merge: method: squash - # ============================================================ - # PR title format help - # ============================================================ - - - name: comment on invalid PR title format - conditions: - - -closed - - -draft - - "-title~=(?i)^\\[(feat|feature|bugfix|fix|refactor|perf|ci|doc|docs|misc|chore|kernel|new.?model|skill|skills|infra)\\]" - actions: - comment: - message: | - ## ⚠️ PR title format required - - Your PR title must start with a type tag in brackets. Examples: - - `[feat] Add new model support` - - `[bugfix] Fix VAE tiling corruption` - - `[refactor] Restructure training pipeline` - - `[perf] Optimize attention kernel` - - `[ci] Update test infrastructure` - - `[infra] Add activation trace hooks` - - `[docs] Add inference guide` - - `[misc] Clean up configs` - - `[new-model] Port Flux2 to FastVideo` - - `[skill] Add add-model agent skill` - - Valid tags: `feat`, `feature`, `bugfix`, `fix`, `refactor`, `perf`, `ci`, `infra`, `doc`, `docs`, `misc`, `chore`, `kernel`, `new-model`, `skill`, `skills` - - Please update your PR title and the merge protection check will pass automatically. - merge_protections_settings: reporting_method: check-runs diff --git a/.github/workflows/community-stale.yml b/.github/workflows/community-stale.yml index f6eaf09c0..4474bb654 100644 --- a/.github/workflows/community-stale.yml +++ b/.github/workflows/community-stale.yml @@ -28,24 +28,7 @@ jobs: days-before-issue-stale: 90 days-before-issue-close: 30 stale-issue-label: 'stale' - stale-issue-message: > - This issue has been automatically marked as stale because it has not - had any activity within 90 days. It will be automatically closed if - no further activity occurs within 30 days. Leave a comment if you - feel this issue should remain open. Thank you! - close-issue-message: > - This issue has been automatically closed due to inactivity. Please - feel free to reopen if you feel it is still relevant. Thank you! days-before-pr-stale: 60 days-before-pr-close: 14 stale-pr-label: 'stale' - stale-pr-message: > - This pull request has been automatically marked as stale because it - has not had any activity within 60 days. It will be automatically - closed if no further activity occurs within 14 days. Leave a comment - if you feel this pull request should remain open. Thank you! - close-pr-message: > - This pull request has been automatically closed due to inactivity. - Please feel free to reopen if you intend to continue working on it. - Thank you! diff --git a/.github/workflows/community-welcome.yml b/.github/workflows/community-welcome.yml deleted file mode 100644 index 8aac52dbe..000000000 --- a/.github/workflows/community-welcome.yml +++ /dev/null @@ -1,56 +0,0 @@ -name: Welcome First-Time Contributors - -on: - issues: - types: [opened] - pull_request_target: - types: [opened] - -permissions: - issues: write - pull-requests: write - -jobs: - welcome: - if: github.repository == 'hao-ai-lab/FastVideo' - runs-on: ubuntu-latest - steps: - - uses: actions/first-interaction@34f15e814fe48ac9312ccf29db4e74fa767cbab7 # v1.3.0 - with: - repo-token: ${{ secrets.GITHUB_TOKEN }} - issue-message: | - Welcome to FastVideo! Thanks for opening your first issue. - - To help us investigate, please include: - - **FastVideo version**: `pip show fastvideo` - - **GPU**: `nvidia-smi` output (GPU model, driver, CUDA version) - - **Python version**: `python --version` - - **OS**: e.g., Ubuntu 22.04 - - If this is a bug, a minimal reproduction script helps us fix it faster. - - Useful links: - - [Documentation](https://hao-ai-lab.github.io/FastVideo) - - [Contributing Guide](https://hao-ai-lab.github.io/FastVideo/contributing/overview/) - - [Slack](https://join.slack.com/t/fastvideo/shared_invite/zt-3f4lao1uq-u~Ipx6Lt4J27AlD2y~IdLQ) - pr-message: | - Welcome to FastVideo! Thanks for your first pull request. - - **How our CI works:** - - PRs run a three-tier CI system: - 1. **Pre-commit** — formatting (yapf), linting (ruff), type checking (mypy). Runs immediately on every PR. - 2. **Fastcheck** — six core GPU lanes run automatically via Buildkite (~10-15 min). - 3. **Merge gate** — a reviewer adds `ready`; changed paths select only the relevant integration, training, golden, or SSIM coverage. - - **Before your PR is reviewed:** - - [ ] `pre-commit run --all-files` passes locally - - [ ] You've added or updated tests for your changes - - [ ] The PR description explains what and why - - If pre-commit fails, a bot comment will explain how to fix it. Fastcheck and merge-gate results appear in the Checks section below. - - **Useful links:** - - [Contributing Guide](https://hao-ai-lab.github.io/FastVideo/contributing/overview/) - - [Development Roadmap](https://github.com/hao-ai-lab/FastVideo/issues/899) - - [Slack](https://join.slack.com/t/fastvideo/shared_invite/zt-3f4lao1uq-u~Ipx6Lt4J27AlD2y~IdLQ) diff --git a/docs/contributing/ci_architecture.md b/docs/contributing/ci_architecture.md index 5f319168b..917ab30ed 100644 --- a/docs/contributing/ci_architecture.md +++ b/docs/contributing/ci_architecture.md @@ -461,8 +461,12 @@ The reusable implementation lives in | Workflow | Trigger | Purpose | |---|---|---| | `community-issue-labeler.yml` | Issue opened or edited | Adds scope/platform labels from issue keywords. | -| `community-welcome.yml` | First contribution | Posts a welcome comment for first-time contributors. | -| `community-stale.yml` | Daily schedule | Marks and closes stale issues and PRs, with exemption labels. | +| `community-stale.yml` | Daily | Labels/closes stale items with exemptions. | + +None of these automations post comments or messages on issues or pull +requests; they only set labels and close stale items. Keep it that way: new +automation must report through checks, commit statuses, or labels instead of +PR/issue comments. ## File Reference