You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rename command from /run-full-ci to /run-skipped-ci
Changes the PR comment command to match the workflow filename for consistency.
**Changes:**
- Update workflow trigger to listen for `/run-skipped-ci`
- Update welcome comment to show `/run-skipped-ci`
- Update README documentation to reference `/run-skipped-ci`
- Update workflow filename reference in docs
The command name now clearly indicates it runs the normally-skipped CI jobs
(minimum versions, examples, Pro tests).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: .github/README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ This directory contains GitHub Actions workflows for continuous integration and
4
4
5
5
## PR Comment Commands
6
6
7
-
### `/run-full-ci` - Run Full CI Suite
7
+
### `/run-skipped-ci` - Run Full CI Suite
8
8
9
9
When you open a PR, CI automatically runs a subset of tests for faster feedback (latest Ruby/Node versions only). To run the **complete CI suite** including all dependency combinations, add a comment to your PR:
10
10
11
11
```
12
-
/run-full-ci
12
+
/run-skipped-ci
13
13
```
14
14
15
15
This command will trigger:
@@ -33,7 +33,7 @@ By default, PRs run a subset of CI jobs to provide fast feedback:
33
33
- Skips example generator tests
34
34
- Skips some Pro package tests
35
35
36
-
This is intentional to keep PR feedback loops fast. However, before merging, you should verify compatibility across all supported versions. The `/run-full-ci` command makes this easy without waiting for the PR to be merged to master.
36
+
This is intentional to keep PR feedback loops fast. However, before merging, you should verify compatibility across all supported versions. The `/run-skipped-ci` command makes this easy without waiting for the PR to be merged to master.
37
37
38
38
### Security & Access Control
39
39
@@ -43,11 +43,11 @@ This is intentional to keep PR feedback loops fast. However, before merging, you
43
43
- Unauthorized access to Pro package tests
44
44
- Potential DoS attacks via repeated CI runs
45
45
46
-
If an unauthorized user attempts to use `/run-full-ci`, they'll receive a message explaining the restriction.
46
+
If an unauthorized user attempts to use `/run-skipped-ci`, they'll receive a message explaining the restriction.
47
47
48
48
### Concurrency Protection
49
49
50
-
Multiple `/run-full-ci` comments on the same PR will cancel in-progress runs to prevent resource waste and duplicate results.
50
+
Multiple `/run-skipped-ci` comments on the same PR will cancel in-progress runs to prevent resource waste and duplicate results.
51
51
52
52
## Testing Comment-Triggered Workflows
53
53
@@ -82,7 +82,7 @@ For more details, see [GitHub's documentation on issue_comment events](https://d
82
82
83
83
### Utility Workflows
84
84
85
-
-**`run-full-ci.yml`** - Triggered by `/run-full-ci` comment on PRs
85
+
-**`run-skipped-ci.yml`** - Triggered by `/run-skipped-ci` comment on PRs
86
86
-**`pr-welcome-comment.yml`** - Auto-comments on new PRs with helpful info
87
87
-**`detect-changes.yml`** - Detects which parts of the codebase changed
88
88
@@ -109,6 +109,6 @@ Many workflows use change detection to skip unnecessary jobs:
109
109
110
110
- Runs all jobs on pushes to `master`
111
111
- Runs only relevant jobs on PRs based on changed files
112
-
- Can be overridden with `workflow_dispatch` or `/run-full-ci` command
112
+
- Can be overridden with `workflow_dispatch` or `/run-skipped-ci` command
113
113
114
114
See `script/ci-changes-detector` for the change detection logic.
0 commit comments