LANGUAGE V1 · FROZEN REFERENCE
Capability registry
274 results · Page 22 of 23
gitdefault branch push
supported — Laygent v1 implements default branch push in its git target.
Requirements and limitations
- Id
- git.default_branch_push
- Status
- supported
- Aliases
- default branch push
- git default branch push
- use default branch push
- add default branch push
- support default branch push
- Evidence
- integrations.py GitHub OAuth and publishing.py Git Data API flow
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
deploy keys
unsupported — Laygent v1 does not implement deploy keys in its git target.
Requirements and limitations
- Id
- git.deploy_keys
- Status
- unsupported
- Aliases
- deploy keys
- git deploy keys
- use deploy keys
- add deploy keys
- support deploy keys
- Evidence
- Limitation
- Laygent v1 does not implement deploy keys in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
discussions
unsupported — Laygent v1 does not implement discussions in its git target.
Requirements and limitations
- Id
- git.discussions
- Status
- unsupported
- Aliases
- discussions
- git discussions
- use discussions
- add discussions
- support discussions
- Evidence
- Limitation
- Laygent v1 does not implement discussions in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
existing repository
unsupported — Laygent v1 does not implement existing repository in its git target.
Requirements and limitations
- Id
- git.existing_repository
- Status
- unsupported
- Aliases
- existing repository
- git existing repository
- use existing repository
- add existing repository
- support existing repository
- Evidence
- Limitation
- Laygent v1 does not implement existing repository in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
github actions
unsupported — Laygent v1 does not implement github actions in its git target.
Requirements and limitations
- Id
- git.github_actions
- Status
- unsupported
- Aliases
- github actions
- CI workflow
- automation workflow
- continuous integration
- git github actions
- use github actions
- add github actions
- support github actions
- Evidence
- Limitation
- Laygent v1 does not implement github actions in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
github oauth
supported — Laygent v1 implements github oauth in its git target.
Requirements and limitations
- Id
- git.github_oauth
- Status
- supported
- Aliases
- github oauth
- git github oauth
- use github oauth
- add github oauth
- support github oauth
- Evidence
- integrations.py GitHub OAuth and publishing.py Git Data API flow
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
history rewrite
unsupported — Laygent v1 does not implement history rewrite in its git target.
Requirements and limitations
- Id
- git.history_rewrite
- Status
- unsupported
- Aliases
- history rewrite
- git history rewrite
- use history rewrite
- add history rewrite
- support history rewrite
- Evidence
- Limitation
- Laygent v1 does not implement history rewrite in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
initial commit
supported — Laygent v1 implements initial commit in its git target.
Requirements and limitations
- Id
- git.initial_commit
- Status
- supported
- Aliases
- initial commit
- git initial commit
- use initial commit
- add initial commit
- support initial commit
- Evidence
- integrations.py GitHub OAuth and publishing.py Git Data API flow
- Limitation
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
issues
unsupported — Laygent v1 does not implement issues in its git target.
Requirements and limitations
- Id
- git.issues
- Status
- unsupported
- Aliases
- issues
- git issues
- use issues
- add issues
- support issues
- Evidence
- Limitation
- Laygent v1 does not implement issues in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
lfs
unsupported — Laygent v1 does not implement lfs in its git target.
Requirements and limitations
- Id
- git.lfs
- Status
- unsupported
- Aliases
- lfs
- git lfs
- use lfs
- add lfs
- support lfs
- Evidence
- Limitation
- Laygent v1 does not implement lfs in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
merges
unsupported — Laygent v1 does not implement merges in its git target.
Requirements and limitations
- Id
- git.merges
- Status
- unsupported
- Aliases
- merges
- git merges
- use merges
- add merges
- support merges
- Evidence
- Limitation
- Laygent v1 does not implement merges in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None
project boards
unsupported — Laygent v1 does not implement project boards in its git target.
Requirements and limitations
- Id
- git.project_boards
- Status
- unsupported
- Aliases
- project boards
- git project boards
- use project boards
- add project boards
- support project boards
- Evidence
- Limitation
- Laygent v1 does not implement project boards in its git target.
- Required slots
- None
- Dependencies
- None
- Conflicts
- None
- Clarify when
- None
- Alternatives
- None