Skip to content

Commit 6554b6b

Browse files
justin808claude
andcommitted
Fix inaccurate workflow list in manual triggering docs
Remove references to non-existent workflows (main.yml and rspec-package-specs.yml). List only the workflows that actually exist and support workflow_dispatch: - package-js-tests.yml (has force_run parameter) - lint-js-and-ruby.yml (has force_run parameter) - playwright.yml (no force_run parameter) Add note that other workflows may support workflow_dispatch and readers should check individual files in .github/workflows/ for configuration and available input parameters. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
1 parent fea69c8 commit 6554b6b

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

.github/read-me.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -148,11 +148,10 @@ gh run list --workflow=package-js-tests.yml
148148
The following workflows can be manually triggered with `workflow_dispatch`:
149149

150150
- **`package-js-tests.yml`** - Accepts `force_run` parameter (boolean) to bypass change detection
151-
- **`main.yml`** - Accepts `force_run` parameter (boolean) to bypass change detection
152151
- **`lint-js-and-ruby.yml`** - Accepts `force_run` parameter (boolean) to bypass change detection
153-
- **`rspec-package-specs.yml`** - Accepts `force_run` parameter (boolean) to bypass change detection
154-
- **`playwright.yml`** - Can be triggered manually
155-
- And others - check individual workflow files for `workflow_dispatch` configuration
152+
- **`playwright.yml`** - Can be triggered manually (does not accept `force_run` parameter)
153+
154+
Other workflows may also support `workflow_dispatch`. Check individual workflow files in `.github/workflows/` for `workflow_dispatch` configuration and available input parameters.
156155

157156
### Why Use Manual Triggers?
158157

0 commit comments

Comments
 (0)