Documentation Request
The imports reference page lists the fields that can be declared in a shared import file and merged into importing workflows.
The github-app top-level field is currently missing from that list, even though it is supported — shared imports that declare github-app correctly merge it into all importing workflows (verified with compiler version v0.65.7).
Suggested Update
Please add github-app to the Allowed Import Fields table/list on the imports reference page, alongside the other top-level fields like network, jobs, etc.
This would confirm for users that the side-repo-ops pattern (using a shared import to centralize github-app configuration) is an officially supported and intended use case.
Why This Matters
The side-repo-ops pattern involves multiple workflows all needing the same github-app credentials. Centralizing this in a shared import (shared/side-repository.md) is a natural refactoring, but users may hesitate to do it if the field is not listed as supported in the docs — or they may incorrectly assume it works like env (which is not supported in imports and is silently ignored; see related issue #26085).
Reported by Claude Code on behalf of the user.
Documentation Request
The imports reference page lists the fields that can be declared in a shared import file and merged into importing workflows.
The
github-apptop-level field is currently missing from that list, even though it is supported — shared imports that declaregithub-appcorrectly merge it into all importing workflows (verified with compiler versionv0.65.7).Suggested Update
Please add
github-appto the Allowed Import Fields table/list on the imports reference page, alongside the other top-level fields likenetwork,jobs, etc.This would confirm for users that the side-repo-ops pattern (using a shared import to centralize
github-appconfiguration) is an officially supported and intended use case.Why This Matters
The side-repo-ops pattern involves multiple workflows all needing the same
github-appcredentials. Centralizing this in a shared import (shared/side-repository.md) is a natural refactoring, but users may hesitate to do it if the field is not listed as supported in the docs — or they may incorrectly assume it works likeenv(which is not supported in imports and is silently ignored; see related issue #26085).Reported by Claude Code on behalf of the user.