Skip to content

docs: re-date custom commands step types blog post to 2026-05-30#2550

Merged
Andriy Knysh (aknysh) merged 2 commits into
mainfrom
osterman/vancouver-v8
May 30, 2026
Merged

docs: re-date custom commands step types blog post to 2026-05-30#2550
Andriy Knysh (aknysh) merged 2 commits into
mainfrom
osterman/vancouver-v8

Conversation

@osterman
Copy link
Copy Markdown
Member

@osterman Erik Osterman (Cloud Posse) (osterman) commented May 30, 2026

what

  • Re-dated the "25+ Interactive Step Types" blog post from 2026-01-03 to 2026-05-30.
  • Renamed the file prefix (git mv, history preserved) and added a matching date: 2026-05-30 frontmatter field.

why

  • Aligns the post's publish date with its actual release timing so it surfaces correctly in the changelog feed.
  • Adds the explicit date: field to match the repo convention (e.g. 2026-05-28-git-yaml-functions.mdx).
  • The slug is unchanged, so the published URL stays the same.

references

  • N/A — docs-only date adjustment, no user-facing code change.

Summary by CodeRabbit

  • Documentation
    • Published comprehensive guide to custom commands and workflow step types, featuring 25+ interactive step types with usage examples, including input collection, output formatting, and variable passing conventions for enhanced automation capabilities.

Review Change Stack

Rename the blog post filename prefix and add a matching `date:`
frontmatter field so the post publishes under today's date. The slug
is unchanged, so the published URL stays the same.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@atmos-pro
Copy link
Copy Markdown
Contributor

atmos-pro Bot commented May 30, 2026

Tip

Atmos Pro  

No affected stacks workflow was detected for this pull request.
If this is expected, no action is needed.
Learn More. Ask AI.

@osterman Erik Osterman (Cloud Posse) (osterman) added the no-release Do not create a new release (wait for additional code changes) label May 30, 2026
@github-actions github-actions Bot added the size/xs Extra small size PR label May 30, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 30, 2026

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 30, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fb7975e7-8352-4d20-ab45-91e1819ecbe3

📥 Commits

Reviewing files that changed from the base of the PR and between 10dc570 and 0c1a295.

📒 Files selected for processing (1)
  • website/blog/2026-05-30-custom-commands-step-types.mdx

📝 Walkthrough

Walkthrough

New blog post documenting the unified execution engine that powers both Atmos workflows and custom commands. Covers 25+ interactive step types across multiple categories (input/selection, UI outputs, rich outputs, terminal/UX actions, command execution), includes usage examples, demonstrates multi-select and input collection patterns, and documents variable passing conventions.

Changes

Blog: Custom Commands and Workflow Step Types

Layer / File(s) Summary
Custom commands and workflow step types blog post
website/blog/2026-05-30-custom-commands-step-types.mdx
New blog post introducing unified execution engine for workflows and custom commands, documenting 25+ interactive step types, usage examples with filter-based multi-select and input collection steps, and variable passing conventions for accessing prior step results.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

no-release

Suggested reviewers

  • aknysh
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: re-dating a blog post file from 2026-01-03 to 2026-05-30 to align publication timing with the changelog feed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch osterman/vancouver-v8

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 30, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.69%. Comparing base (402851e) to head (670a56b).

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #2550      +/-   ##
==========================================
+ Coverage   78.66%   78.69%   +0.02%     
==========================================
  Files        1184     1184              
  Lines      113107   113107              
==========================================
+ Hits        88974    89005      +31     
+ Misses      19244    19212      -32     
- Partials     4889     4890       +1     
Flag Coverage Δ
unittests 78.69% <ø> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 5 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@aknysh Andriy Knysh (aknysh) merged commit 3023846 into main May 30, 2026
59 checks passed
@aknysh Andriy Knysh (aknysh) deleted the osterman/vancouver-v8 branch May 30, 2026 23:32
@atmos-pro
Copy link
Copy Markdown
Contributor

atmos-pro Bot commented May 30, 2026

Tip

Atmos Pro  

No affected stacks workflow was detected for this pull request.
If this is expected, no action is needed.
Learn More. Ask AI.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 2, 2026

These changes were released in v1.221.0-rc.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release Do not create a new release (wait for additional code changes) size/xs Extra small size PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants