update github action docs to match ambient-action v2#1244
update github action docs to match ambient-action v2#1244vishsanghishetty wants to merge 1 commit intoambient-code:mainfrom
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughUpdated GitHub Action documentation and example workflows: clarified input/output descriptions and wording for several action inputs ( Changes
🚥 Pre-merge checks | ✅ 7 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (7 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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. Comment |
5b2c611 to
205b873
Compare
the docs were pinned to v0.0.2 and missing several inputs/outputs that have been added since. syncs the inputs table (adds session-name, stop-on-run-finished, poll-timeout), outputs table (adds session-url), fixes the timeout description, and bumps all examples to @v2. closes ambient-code#1232 Signed-off-by: Vishali <vsanghis@redhat.com>
205b873 to
c9d5ed7
Compare
Closes #1232
Why
The GitHub Action docs were pinned to
v0.0.2and hadn't been updated since. Several inputs, an output, and thetimeoutsemantics have all changed inambient-code/ambient-action— the docs didn't reflect any of it.What changed
Inputs table
session-namestop-on-run-finishedpoll-timeoutwait: true)timeoutaction.yml)api-token,project,prompt,wait,poll-interval— aligned wording withaction.ymlOutputs table
session-urlVersion refs
@v0.0.2→@v2(acrossgithub-action.mdandbugfix.md)(v0.0.2)from the intro paragraphFiles touched
docs/src/content/docs/extensions/github-action.mddocs/src/content/docs/workflows/bugfix.mdHow I tested
Compared every input and output in the updated docs against
action.ymlline by line — all 17 inputs and 5 outputs match. No code changes, so no lint/test/tsc applicable. Astro build will run in CI (couldn't build locally — needs Node 22+, local is Node 20).Summary by CodeRabbit