{"owner":"peaceiris","repo":"actions-gh-pages","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# Repository Guidelines\n\n## Agent-Specific Instructions\n\nUse English for repository-facing content, including documentation, code comments, commit messages, and pull request title/body/comments, unless the task explicitly requires another language.\n\n## Project Structure & Module Organization\n\nThis is a TypeScript GitHub Action for publishing GitHub Pages. Source files live\nin `src/`; `src/index.ts` is the entry point and delegates to modules such as\n`get-inputs.ts`, `git-utils.ts`, and `set-tokens.ts`. Tests live in `__tests__/`,\nwith static fixtures under `__tests__/fixtures/`. Documentation is in `README.md`\nand `CHANGELOG.md`; screenshots and docs assets are in `images/`. `action.yml`\ndefines action inputs and points to generated `lib/index.js`.\n\n## Build, Test, and Development Commands\n\nUse Node `>=20.11.0` and npm `>=10.2.4`.\n\n- `npm ci`: install dependencies from `package-lock.json`.\n- `npm run all`: run format, lint, and Jest tests.\n- `npm run build`: bundle `src/index.ts` into `lib/` with `ncc`.\n- `npm run tsc`: run the TypeScript compiler checks.\n- `npm test`: run Jest with coverage and verbose output.\n- `npm run lint` / `npm run lint:fix`: check or fix ESLint issues.\n- `npm run format:check` / `npm run format`: check or apply Prettier formatting.\n\nWhen changing `src/`, build locally if needed for verification, but do not commit\n`lib/index.js` in normal changes. Generated `lib/index.js` is placed on `main`\nonly during releases.\n\n## Coding Style & Naming Conventions\n\nWrite strict TypeScript and keep module boundaries small. Use 2-space\nindentation, semicolons, single quotes, no trailing commas, and a 100-character\nprint width, matching `.prettierrc.json`. Test files use `*.test.ts`. Prefer\nnames that match action inputs where relevant, for example `publish_branch`.\n\n## Testing Guidelines\n\nJest with `ts-jest` is the test framework. Add focused tests in `__tests__/` near\nrelated behavior, and place reusable filesystem samples in `__tests__/fixtures/`.\nRun `npm test` for coverage, and use `npm run all` before opening a pull request\nthat touches TypeScript source or tests.\n\n## Commit & Pull Request Guidelines\n\nRecent history follows conventional commit prefixes such as `fix(deps):`,\n`chore(deps):`, `docs:`, and `ci:`. Use a concise imperative subject and include\nthe scope when it clarifies the affected area. Pull requests should describe the\nchange, link related issues, list verification commands, and include screenshots\nonly for documentation image changes. Mention any action input or behavior change\nexplicitly so reviewers can assess compatibility.\n\n## Security & Configuration Tips\n\nDo not commit tokens, private keys, or generated secrets. Treat inputs such as\n`deploy_key`, `github_token`, and `personal_token` as sensitive, and keep examples\nlimited to placeholder values.\n"},"files":{"AGENTS.md":"# Repository Guidelines\n\n## Agent-Specific Instructions\n\nUse English for repository-facing content, including documentation, code comments, commit messages, and pull request title/body/comments, unless the task explicitly requires another language.\n\n## Project Structure & Module Organization\n\nThis is a TypeScript GitHub Action for publishing GitHub Pages. Source files live\nin `src/`; `src/index.ts` is the entry point and delegates to modules such as\n`get-inputs.ts`, `git-utils.ts`, and `set-tokens.ts`. Tests live in `__tests__/`,\nwith static fixtures under `__tests__/fixtures/`. Documentation is in `README.md`\nand `CHANGELOG.md`; screenshots and docs assets are in `images/`. `action.yml`\ndefines action inputs and points to generated `lib/index.js`.\n\n## Build, Test, and Development Commands\n\nUse Node `>=20.11.0` and npm `>=10.2.4`.\n\n- `npm ci`: install dependencies from `package-lock.json`.\n- `npm run all`: run format, lint, and Jest tests.\n- `npm run build`: bundle `src/index.ts` into `lib/` with `ncc`.\n- `npm run tsc`: run the TypeScript compiler checks.\n- `npm test`: run Jest with coverage and verbose output.\n- `npm run lint` / `npm run lint:fix`: check or fix ESLint issues.\n- `npm run format:check` / `npm run format`: check or apply Prettier formatting.\n\nWhen changing `src/`, build locally if needed for verification, but do not commit\n`lib/index.js` in normal changes. Generated `lib/index.js` is placed on `main`\nonly during releases.\n\n## Coding Style & Naming Conventions\n\nWrite strict TypeScript and keep module boundaries small. Use 2-space\nindentation, semicolons, single quotes, no trailing commas, and a 100-character\nprint width, matching `.prettierrc.json`. Test files use `*.test.ts`. Prefer\nnames that match action inputs where relevant, for example `publish_branch`.\n\n## Testing Guidelines\n\nJest with `ts-jest` is the test framework. Add focused tests in `__tests__/` near\nrelated behavior, and place reusable filesystem samples in `__tests__/fixtures/`.\nRun `npm test` for coverage, and use `npm run all` before opening a pull request\nthat touches TypeScript source or tests.\n\n## Commit & Pull Request Guidelines\n\nRecent history follows conventional commit prefixes such as `fix(deps):`,\n`chore(deps):`, `docs:`, and `ci:`. Use a concise imperative subject and include\nthe scope when it clarifies the affected area. Pull requests should describe the\nchange, link related issues, list verification commands, and include screenshots\nonly for documentation image changes. Mention any action input or behavior change\nexplicitly so reviewers can assess compatibility.\n\n## Security & Configuration Tips\n\nDo not commit tokens, private keys, or generated secrets. Treat inputs such as\n`deploy_key`, `github_token`, and `personal_token` as sensitive, and keep examples\nlimited to placeholder values.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Repository Guidelines\n\n## Agent-Specific Instructions\n\nUse English for repository-facing content, including documentation, code comments, commit messages, and pull request title/body/comments, unless the task explicitly requires another language.\n\n## Project Structure & Module Organization\n\nThis is a TypeScript GitHub Action for publishing GitHub Pages. Source files live\nin `src/`; `src/index.ts` is the entry point and delegates to modules such as\n`get-inputs.ts`, `git-utils.ts`, and `set-tokens.ts`. Tests live in `__tests__/`,\nwith static fixtures under `__tests__/fixtures/`. Documentation is in `README.md`\nand `CHANGELOG.md`; screenshots and docs assets are in `images/`. `action.yml`\ndefines action inputs and points to generated `lib/index.js`.\n\n## Build, Test, and Development Commands\n\nUse Node `>=20.11.0` and npm `>=10.2.4`.\n\n- `npm ci`: install dependencies from `package-lock.json`.\n- `npm run all`: run format, lint, and Jest tests.\n- `npm run build`: bundle `src/index.ts` into `lib/` with `ncc`.\n- `npm run tsc`: run the TypeScript compiler checks.\n- `npm test`: run Jest with coverage and verbose output.\n- `npm run lint` / `npm run lint:fix`: check or fix ESLint issues.\n- `npm run format:check` / `npm run format`: check or apply Prettier formatting.\n\nWhen changing `src/`, build locally if needed for verification, but do not commit\n`lib/index.js` in normal changes. Generated `lib/index.js` is placed on `main`\nonly during releases.\n\n## Coding Style & Naming Conventions\n\nWrite strict TypeScript and keep module boundaries small. Use 2-space\nindentation, semicolons, single quotes, no trailing commas, and a 100-character\nprint width, matching `.prettierrc.json`. Test files use `*.test.ts`. Prefer\nnames that match action inputs where relevant, for example `publish_branch`.\n\n## Testing Guidelines\n\nJest with `ts-jest` is the test framework. Add focused tests in `__tests__/` near\nrelated behavior, and place reusable filesystem samples in `__tests__/fixtures/`.\nRun `npm test` for coverage, and use `npm run all` before opening a pull request\nthat touches TypeScript source or tests.\n\n## Commit & Pull Request Guidelines\n\nRecent history follows conventional commit prefixes such as `fix(deps):`,\n`chore(deps):`, `docs:`, and `ci:`. Use a concise imperative subject and include\nthe scope when it clarifies the affected area. Pull requests should describe the\nchange, link related issues, list verification commands, and include screenshots\nonly for documentation image changes. Mention any action input or behavior change\nexplicitly so reviewers can assess compatibility.\n\n## Security & Configuration Tips\n\nDo not commit tokens, private keys, or generated secrets. Treat inputs such as\n`deploy_key`, `github_token`, and `personal_token` as sensitive, and keep examples\nlimited to placeholder values.\n","category":"root","tokens":708}]}