Skip to content

🔇 Denoiser: Add rule for Vercel CI release steps #146

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lucasew wants to merge 1 commit into
base: master
Choose a base branch
from
Open

🔇 Denoiser: Add rule for Vercel CI release steps #146

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .jules/CONSISTENTLY_IGNORED.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
## IGNORE: No Release/Artifact Steps in CI for Vercel

**- Pattern:** Adding `Release` or `Artifacts` jobs/steps to `.github/workflows/autorelease.yml`.
**- Justification:** Vercel deployments manage their own releases. The `autorelease.yml` workflow should strictly handle CI checks (lint/test) and tag creation, but not artifact uploads or GitHub Releases modification, as these are intentionally omitted for Vercel-based projects.
**- Files Affected:** `.github/workflows/autorelease.yml`
Comment on lines +3 to +5
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Feb 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For better readability and to adhere to standard Markdown conventions, it's recommended to format this section as a bulleted list. This makes the structure clearer by separating the labels from the content more distinctly.

Suggested change
**- Pattern:** Adding `Release` or `Artifacts` jobs/steps to `.github/workflows/autorelease.yml`.
**- Justification:** Vercel deployments manage their own releases. The `autorelease.yml` workflow should strictly handle CI checks (lint/test) and tag creation, but not artifact uploads or GitHub Releases modification, as these are intentionally omitted for Vercel-based projects.
**- Files Affected:** `.github/workflows/autorelease.yml`
* **Pattern:** Adding `Release` or `Artifacts` jobs/steps to `.github/workflows/autorelease.yml`.
* **Justification:** Vercel deployments manage their own releases. The `autorelease.yml` workflow should strictly handle CI checks (lint/test) and tag creation, but not artifact uploads or GitHub Releases modification, as these are intentionally omitted for Vercel-based projects.
* **Files Affected:** `.github/workflows/autorelease.yml`