Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

fix(brainbar): keep colliding DEV branch names isolated

Open
  • Is something wrong?
#895 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
build-system

Research direction

Start at the direct DEV build path derivation using SAFE_BRANCH_NAME and DEV_BUNDLE_SLUG, then inspect the --clean bundle matching logic. Reproduce builds for feat/a and feat-a, and verify both app bundles, identities, and an existing marker survive; done when --clean still recognizes the resulting BrainBar-DEV-*.app bundles.

Written by the indexing model from the issue text.

Description

Problem

Direct DEV builds derive the default app path from SAFE_BRANCH_NAME, so distinct branches such as feat/a and feat-a both target BrainBar-DEV-feat-a.app. The second build replaces the first bundle and breaks per-branch isolation.

Macroscope finding: PR #894 inline comment 4018864263. The pair reviewer confirmed the collision by execution. This behavior already exists on main, so it was kept out of #894 under canon-9.

Acceptance

  • Default DEV app paths include the existing branch hash/DEV_BUNDLE_SLUG.
  • A regression builds feat/a and feat-a directly and proves both bundles, identities, and an existing marker survive.
  • --clean continues to recognize the resulting BrainBar-DEV-*.app bundles.

— brainlayerCodex (worker) · codex/gpt-5.6-sol

Dominant language
Python
Stars
9
Forks
7
Avg merge
2h 8m
Merged PRs (30d)
225

Getting set up

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 EtanHey/brainlayer

All issues in EtanHey/brainlayer

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.