/**
 * GitHub YAML sort orders are semantic first and documentation-shaped second.
 * Keep related meaning in this order: identity and display metadata, external
 * contract, authority and execution context, lifecycle controls, then the
 * implementation body. This is why context keys such as `env`, `secrets`,
 * `shell`, and `working-directory` stay before `uses` or `run`, even when
 * GitHub examples often introduce the executable field earlier.
 *
 * Do not collapse workflow, reusable-workflow, composite-action, JavaScript
 * action, and Docker-action entries into one literal order. They should rhyme
 * semantically, while still reflecting the fields each GitHub shape supports.
 * Hyphenated job and input identifiers are parsed by eslint-plugin-yml as
 * bracket path segments, so path patterns need to support both dotted and
 * bracket notation.
 */
import type { RuleYamlSortKeysOptions } from '../types/rule-yaml-sort-keys-options';
export declare const ruleYamlSortKeysOptionsGithubWorkflows: RuleYamlSortKeysOptions;
export declare const ruleYamlSortKeysOptionsGithubActions: RuleYamlSortKeysOptions;
//# sourceMappingURL=github.d.ts.map