Skip to content

[Bug]: daytona.js missing from packages/cli/.gitignore #3348

Description

@la14-1

Bug

packages/cli/.gitignore ignores all the cloud bundle build artifacts (aws.js, hetzner.js, digitalocean.js, gcp.js, local.js, sprite.js, cli.js) — but daytona.js is missing from the list. When a contributor runs bun run packages/cli/build-clouds.ts locally, daytona.js ends up staged by git add -A while the others don't, which is a footgun (the committed artifact would be ~3 MB and drift from source).

Expected

Add daytona.js to packages/cli/.gitignore next to the other cloud bundles.

How I hit this

Noticed while rebasing #3346 — git add -A after a build staged packages/cli/daytona.js even though all the other cloud bundle artifacts were correctly ignored.

Fix

One-line addition to packages/cli/.gitignore:

daytona.js

Filed from Slack by SPA

Activity

  1. added
    bugSomething isn't working
    pending-reviewIssue awaiting initial review
    under-reviewIssue is being reviewed by the team
    and removed
    pending-reviewIssue awaiting initial review
    on Apr 24, 2026
  2. la14-1 commented on Apr 24, 2026

    @la14-1
    CollaboratorAuthor

    Confirmed — daytona.js is missing from packages/cli/.gitignore while all other cloud bundle artifacts are listed. This is a valid bug that can cause accidental staging of a ~3 MB build artifact.

    Delegating to code-health for the one-line fix.

    -- refactor/community-coordinator

  3. added
    in-progressIssue is being actively worked on
    and removed
    under-reviewIssue is being reviewed by the team
    on Apr 24, 2026
  4. la14-1 commented on Apr 24, 2026

    @la14-1
    CollaboratorAuthor

    Fix in #3349.

    -- refactor/community-coordinator

  5. added 2 commits that reference this issue on Apr 26, 2026
    53b9c1b
    3947807
  6. la14-1 commented on May 2, 2026

    @la14-1
    CollaboratorAuthor

    Tracked — fix is in progress in PR #3349.

    -- refactor/community-coordinator

  7. added a commit that references this issue on May 3, 2026
    93839b9
  8. la14-1 commented on May 7, 2026

    @la14-1
    CollaboratorAuthor

    Fix in #3349.

    -- refactor/community-coordinator

  9. la14-1 commented on May 7, 2026

    @la14-1
    CollaboratorAuthor

    Fix in #3349.

    -- refactor/community-coordinator

  10. added a commit that references this issue on May 9, 2026
    2b85e74
  11. la14-1 commented on May 9, 2026

    @la14-1
    CollaboratorAuthor

    Fix in progress: #3349

    -- refactor/community-coordinator

  12. added 3 commits that reference this issue on May 11, 2026
    4c95af0
    af549fb
    41867ac
  13. la14-1 commented on May 14, 2026

    @la14-1
    CollaboratorAuthor

    Fix in #3349.

    -- refactor/community-coordinator

  14. added a commit that references this issue on Jun 6, 2026
    fe137e4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingin-progressIssue is being actively worked onunder-reviewIssue is being reviewed by the team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions