ci: trigger CI on PR creation, gate build-docs to push/dispatch only #169
No Reviewers
Labels
Clear labels
Area/CI
Area/Completions
Area/Components
Area/Config
Area/Docs
Area/Functions
Area/Integrations
Area/Prompt & Theme
Area/Scripts
Area/Tests
Compat/Breaking
Kind/Bug
Kind/Chore
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Performance
Kind/Refactor
Kind/Security
Kind/Testing
good first issue
help wanted
.github/workflows and repository automation
completions/ - tab-completion scripts
The opinionated-component system (C1-C6)
config.fish and conf.d/ - startup and environment
docs/manual/ and the generated manual, man page, and site
functions/ - user-facing functions and helpers
integrations/ - third-party tool wiring
themes/ and prompt appearance
scripts/ - standalone helper scripts
tests/ - the syntax lint and functional suite
Breaking change that won't be backward compatible
Something is not working
Tooling, dependencies, and housekeeping
Documentation changes
Improve existing functionality
New functionality
Makes existing behavior faster or lighter
Restructures code without changing behavior
This is security issue
Issue or pull request related to testing
Well-scoped and self-contained; a good place to start
Maintainer is looking for someone to pick this up
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Medium
3
The priority is medium
Priority
Low
4
The priority is low
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Milestone
No items
No Milestone
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: rootiest/fish-config#169
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
.github/workflows/ci.ymlonly had apush: branches: [main]trigger — nopull_requesttrigger at all, so PRs never got automated CI feedback; the only gate was whatever a human (or agent) ran locally before merge. This adds one.pull_request: branches: [main]trigger, sharing the samepaths:filter aspushvia a YAML anchor (&ci-paths/*ci-paths) instead of duplicating the list.build-docsjob gainsgithub.event_name != 'pull_request'to itsif:. It auto-commits generated docs (fish-config.md,.1, the component registry) straight to the checked-out ref and deploys the Cloudflare Pages production site with--branch=main— neither should run against PR content, which isn'tmainyet.testjob's existingif:(Gitea-only,racknerd-minirunner) needed no change — it already gates correctly for both event types.Verification
python3 -c "import yaml; yaml.safe_load(open('.github/workflows/ci.yml'))"— valid YAML.python3 docs/verify-manual.py— 84/84 passed.fish tests/run-tests.fish— 757/757 assertions passed, exit 0.