Skip to content

fix: allow setting default value for [Default] environment in set-default command#85

Open
jdwyah wants to merge 1 commit intomainfrom
jd/fix-set-default-allow-default-env
Open

fix: allow setting default value for [Default] environment in set-default command#85
jdwyah wants to merge 1 commit intomainfrom
jd/fix-set-default-allow-default-env

Conversation

@jdwyah
Copy link
Contributor

@jdwyah jdwyah commented Mar 5, 2026

Summary

  • Adds allowDefaultEnvironment: true to the getEnvironment() call in set-default command
  • This shows [Default] as an option in the interactive environment picker, allowing users to set base-level defaults
  • Bumps version to 0.0.15

Problem

When using reforge set-default interactively, users could only select environment-specific values (Production, Staging, etc.) but not the base [Default] value. The workaround was to use --environment=[default] flag directly.

Test plan

  • Existing tests pass (284 passing)
  • Manual test: reforge set-default now shows [Default] in the environment picker

🤖 Generated with Claude Code

…ault command

The interactive environment picker wasn't showing the [Default] option,
preventing users from setting base-level defaults via the CLI interactive mode.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant