Fix typos in test config files @osterman (#1310)
## what - fix spelling in indentation scenario README - fix comments in demo vendor test case - fix vendor scenario comments - fix empty dir tests wording - fix log level validation wording - fix website docs typos across MDX fileswhy
- Testing OpenAI Codex
- We were less strict about spelling validation prior to introducing CodeRabbit and some of our Golang Lint CI formatting.
https://chatgpt.com/codex/tasks/task_b_6852e489919c833295b1ce0e8e31910c
Add `AGENTS.md` instructions @osterman (#1311)
## what - clarify Go formatting guidelines in `AGENTS.md`https://chatgpt.com/codex/tasks/task_b_6852ea1ad4f48332ab348ca5a790f149
Summary by CodeRabbit
- Documentation
- Added a new AGENTS.md file outlining developer workflow, code formatting, testing, and pull request best practices for the Golang CLI project.
add pager to describe workflow @samtholiya (#1266)
## what- Updated describe workflows with pager
why
- Makes easier for users to view the content
references
Summary by CodeRabbit
-
New Features
- Enhanced the "describe workflows" command with improved flag parsing, validation, and default values.
- Added support for output in both YAML and JSON formats, with flexible output types ("list", "map", or "all").
- Introduced paged and TTY-aware output display for easier viewing of workflow descriptions.
- Added explicit handling of the "pager" flag in describe stack and describe affected commands for better terminal output control.
-
Bug Fixes
- Improved error handling for invalid flag values in the "describe workflows" command.
-
Tests
- Added comprehensive unit tests for flag parsing, argument handling, and command execution.
-
Refactor
- Modularized the "describe workflows" command for better maintainability and easier testing.
- Refined pager usage in describe stacks command to allow injection of custom pager instances.
- Removed unsupported flag type test to streamline test coverage.
update posthog config @osterman (#1280)
## what - track to a atmos open source projectwhy
- keep data separate from marketing website
Summary by CodeRabbit
- Chores
- Updated analytics configuration for improved tracking.
Fix feature-releases environment branch protection policy @goruha (#1298)
## what * Use `**/*` at `feature-releases` environment policy protectionwhy
*does not includes/char
references
Summary by CodeRabbit
- Chores
- Updated branch matching rules to support nested branch names for deployments.
Added feature-release environment @goruha (#1297)
## what * Added feature-release environmentwhy
- Required by
feature releasefrom PRs
references
Summary by CodeRabbit
- Chores
- Added a new "feature-releases" environment to deployment settings, enabling deployments from any branch.
🚀 Enhancements
fix sections flag not working @samtholiya (#1313)
## what- Fixes section flag not working
why
references
Summary by CodeRabbit
- New Features
- The "sections" option now supports specifying multiple component sections at once, allowing users to input several values for greater flexibility.
🐛 Bug Fixes
DEV-3331: Release From Branch @milldr (#1281)
## what - Optionally create a prerelease from a feature branch if PR have `release/feature` label - Release created on PR synchronizationwhy
- Prereleases can be used to publish a feature
references
Summary by CodeRabbit
- Chores
- Updated automated workflow to run release jobs on pull requests labeled with "release/feature".
- Added a new label "release/feature" for managing feature releases.
- Added a prerelease step and environment configuration to the release process.
- Introduced a new deployment environment named "demo" allowing deployment from all branches.