Skip to content

release: docker-compose .env fix + CLAUDE.md branching policy#44

Merged
Setounkpe7 merged 2 commits into
mainfrom
dev
May 21, 2026
Merged

release: docker-compose .env fix + CLAUDE.md branching policy#44
Setounkpe7 merged 2 commits into
mainfrom
dev

Conversation

@Setounkpe7

Copy link
Copy Markdown
Owner

Summary

Promote two small dev-quality changes to production:

No runtime/behavior change. Both PRs already passed the full security gate on dev.

Test plan

  • CI security gate passes on this PR (same set of 7+ checks).
  • Railway redeploys cleanly on merge to main — no env or migration impact expected.

🤖 Generated with Claude Code

Setounkpe7 and others added 2 commits May 20, 2026 20:05
docker compose up --build used to fail right after git clone because
env_file pointed at a gitignored .env that doesn't exist on first run.
Switch to the long form with required: false so a missing .env is fine,
and add a `cp .env.example .env` line to the Quick Start for users who
want to populate ADMIN_API_KEY or GITHUB_TOKEN.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
)

Codifies the workflow contributors (human or agent) must follow:
- never commit directly on main or dev
- any task starts on a feat|fix|chore|docs|hotfix/* branch cut from dev
- flow is feat/* -> dev -> main

Also documents the graphify knowledge graph so Claude reads
graphify-out/GRAPH_REPORT.md before answering architecture questions.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Setounkpe7 Setounkpe7 merged commit 79d696e into main May 21, 2026
11 checks passed
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