GitHub (gh CLI)

Defaults & Constraints

• Use gh CLI for all GitHub interactions.
• Set GH_PAGER=cat for all gh calls to avoid interactive pagers.
• The repo is elastic/kibana; when not inside a local clone, prefer -R elastic/kibana for gh subcommands. For gh api, -R is not supported; use explicit repos/elastic/kibana/... endpoints or set GH_REPO=elastic/kibana when using {owner}/{repo} placeholders.
• Follow repository merge settings (squash/rebase/merge); do not enforce a merge strategy.
• Never merge into the base branch via CLI; merges happen via the GitHub UI.

First Actions

1. Resolve the exact target repo/object (PR, issue, comment thread, release) before mutating anything.

PR Targeting

• If the user uses implicit-current phrasing ("this PR", "current PR", "PR for this branch") and does not specify a PR URL/number, resolve the PR for the current branch: gh pr view --json number -q .number.
• Do not assume an unspecified GitHub task targets the current branch PR unless the wording clearly implies the current PR.