Skip to content

fix(cli): use named Space colors in generated README frontmatter #1016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sergiopaniego wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(cli): use named Space colors in generated README frontmatter #1016

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/openenv/cli/commands/push.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -421,8 +421,8 @@ def _prepare_staging_directory(
frontmatter = f"""---
title: {env_name.replace("_", " ").title()} Environment Server
emoji: 🔊
colorFrom: '#00C9FF'
colorTo: '#1B2845'
colorFrom: blue

@cursor cursor Bot Jul 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Correct fix. HF's Spaces config reference only accepts named colors (red, yellow, green, blue, indigo, purple, pink, gray); the previous hex values were rejected by Hub metadata validation. blue/indigo are valid and also match the named-color list openenv init already uses (init.py:204), so both frontmatter generators are now consistent. Verified: ruff/usort pass and this is valid YAML.

colorTo: indigo
sdk: docker
pinned: false
app_port: 8000
Expand Down
Loading