Skip to content

chore: remove Blacksmith workflow#257

Merged
leoisadev1 merged 1 commit into
mainfrom
chore/remove-blacksmith-workflow
Nov 8, 2025
Merged

chore: remove Blacksmith workflow#257
leoisadev1 merged 1 commit into
mainfrom
chore/remove-blacksmith-workflow

Conversation

@leoisadev1

Copy link
Copy Markdown
Member

Removing Blacksmith CI/CD workflow - not needed since cache issue is resolved.

Cache corruption issue resolved with Vercel-native builds.
Build time: ~42s locally, expected ~2-3min on Vercel.

Removing Blacksmith CI/CD workflow files added in PR #255.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 8, 2025

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
openchat-web Error Error Nov 8, 2025 2:47am

@leoisadev1 leoisadev1 merged commit dbe7df7 into main Nov 8, 2025
3 of 4 checks passed

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Greptile Overview

Greptile Summary

Removes the Blacksmith CI/CD workflow that was added just hours earlier, reverting to direct Vercel deployment after resolving the cache issue that prompted its creation.

Key changes:

  • Deleted .github/workflows/ci-cd.yml (141 lines) - Blacksmith-powered workflow with tests, builds, and Vercel deploys
  • Deleted .github/workflows/README.md (153 lines) - Setup documentation for Blacksmith integration
  • .github/workflows/prod-canary.yml remains active for production health checks

Timeline context:

  1. Commit cf20778 added Blacksmith workflow to work around Vercel's cache/upload limits
  2. Commit a2c0bdb fixed the root cache issue
  3. This PR removes Blacksmith since the original problem is resolved

Minor issue found:

  • apps/web/next.config.mjs:229 contains an outdated comment referencing "Re-enable only on faster CI (Blacksmith)" that should be updated

Confidence Score: 4/5

  • Safe to merge with one minor cleanup needed
  • The workflow removal is clean and justified since the cache issue is resolved. Score is 4/5 (not 5) due to the outdated Blacksmith reference in next.config.mjs:229 that should be updated to prevent confusion
  • Check apps/web/next.config.mjs:229 for the outdated comment reference to Blacksmith

Important Files Changed

File Analysis

Filename Score Overview
.github/workflows/README.md 5/5 Removed Blacksmith workflow documentation - clean deletion
.github/workflows/ci-cd.yml 5/5 Removed Blacksmith CI/CD workflow - clean deletion, existing prod-canary.yml still active

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub
    participant BC as Blacksmith CI (removed)
    participant PC as prod-canary.yml
    participant V as Vercel

    Note over Dev,V: BEFORE (with Blacksmith workflow)
    Dev->>GH: Push to main / Open PR
    GH->>BC: Trigger ci-cd.yml
    BC->>BC: Lint, Type Check, Tests
    BC->>BC: Build Next.js app
    BC->>V: Deploy to Vercel
    BC->>GH: Comment preview URL (PRs)
    GH->>PC: Trigger prod-canary.yml
    PC->>PC: Run canary tests

    Note over Dev,V: AFTER (Blacksmith removed)
    Dev->>GH: Push to main / Open PR
    GH->>V: Direct Vercel integration
    V->>V: Build and deploy
    GH->>PC: Trigger prod-canary.yml
    PC->>PC: Run canary tests
Loading

Additional Comments (1)

  1. apps/web/next.config.mjs, line 229 (link)

    style: Outdated comment references Blacksmith CI which was just removed

2 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant