[github-docs-seo] Improve GitHub Docs discoverability for GitHub Agentic Workflows in repository automation guidance #67112

[
  {
    "request": "Scan the issue tracker and recent commits, group similar bug reports, and open a triage summary with suggested priorities and likely owners.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Projects + summary issue",
        "reason": "Best overall fit: use a Project to group related bugs, add Priority and Owner fields, link recent commit evidence, then open one issue with the triage summary and recommended assignments."
      },
      {
        "rank": 2,
        "name": "Automated triage via GitHub Actions + GitHub CLI/API",
        "reason": "Best for repeatable scanning: a workflow can query recent issues and commits, cluster similar reports by labels/text, and open or update a triage issue automatically with suggested priorities and owners."
      },
      {
        "rank": 3,
        "name": "Manual issue search/labels/milestones + triage issue",
        "reason": "Best lightweight option: search and label similar bugs, use milestones or assignees for likely owners, and create a single issue summarizing themes, severity, and next actions without setting up automation."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "In this Node.js monorepo, find outdated dependencies, prepare safe upgrade branches for patch and minor releases, run the relevant tests, and summarize any breaking changes.",
    "options": [
      {
        "rank": 1,
        "name": "Dependabot version updates with grouped patch/minor PRs and CI",
        "reason": "Best fit if you want mostly built-in automation: Dependabot can detect outdated npm dependencies, open update branches/PRs, separate or group patch vs minor updates, and rely on GitHub Actions/branch protection to run monorepo tests. Its PR metadata also helps summarize release notes and potential breaking changes."
      },
      {
        "rank": 2,
        "name": "GitHub Copilot coding agent handling dependency-update PRs",
        "reason": "Best fit when you want an agent to do the full workflow end to end: inspect the monorepo, choose safe patch/minor upgrades, create branches, run targeted tests, and write a human summary of breaking-change risk. It is more adaptive than Dependabot when workspaces, custom scripts, or selective test scopes are involved."
      },
      {
        "rank": 3,
        "name": "Custom GitHub Actions workflow for scheduled dependency audit and upgrade branches",
        "reason": "Best fit when you need full control: a scheduled or manually triggered Actions workflow can run npm/pnpm/yarn outdated checks across the monorepo, create separate patch/minor branches, execute the relevant test commands, and publish a structured summary. It requires more setup but handles repo-specific policies cleanly."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Generate a weekly engineering report from merged pull requests, closed issues, and changelog entries, then post a draft summary in markdown for the team.",
    "options": [
      {
        "rank": 1,
        "name": "Scheduled GitHub Actions workflow that posts a draft Discussion",
        "reason": "Best fit for a weekly report: GitHub Actions can run on a schedule, query merged PRs and closed issues via the GitHub API/CLI, read changelog entries from the repo, and publish a markdown draft for the team in one automated GitHub-native flow."
      },
      {
        "rank": 2,
        "name": "Scheduled GitHub Actions workflow that opens or updates an issue",
        "reason": "Also highly compatible and fully GitHub-native. Use the same weekly data collection, but post the markdown draft as an issue for easy review, edits, assignments, and historical tracking if Discussions are not preferred."
      },
      {
        "rank": 3,
        "name": "GitHub Release draft with generated notes plus manual issue tracking summary",
        "reason": "Useful when the team already treats releases as the weekly communication artifact. It is weaker for closed issues and custom changelog synthesis, but still gives a GitHub-supported markdown draft centered on merged work."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Review the docs in this Python package for commands and config options that no longer match the code, update them, and include examples for the most common workflows.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Copilot coding agent on a branch/PR",
        "reason": "Best end-to-end fit: it can inspect the Python package, compare docs to implementation, update documentation, add workflow examples, and deliver the result as a reviewable PR."
      },
      {
        "rank": 2,
        "name": "GitHub Codespaces with GitHub Copilot Chat/Agent",
        "reason": "Strong fit when you want an interactive session: Codespaces provides a ready Python dev environment, and Copilot can help audit commands/config options, rewrite docs, and run validation while you steer."
      },
      {
        "rank": 3,
        "name": "GitHub pull request workflow with GitHub Actions validation",
        "reason": "Best as a controlled docs-refresh process: make the edits in a PR and use Actions to run tests, docs checks, or example verification so updated command/config docs stay aligned with the code."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Run the fastest useful test subsets for files changed in the current branch, retry flaky failures once, and produce a short failure report with likely root causes.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Actions pull_request workflow with changed-file detection, impacted-test selection, one retry loop, and job summary",
        "reason": "Best fit: fully automates the exact request on every branch/PR, can diff against the base branch, run only impacted tests, retry failures once in-script, and publish a short root-cause report in the workflow summary."
      },
      {
        "rank": 2,
        "name": "Reusable GitHub Actions workflow called from repository-specific PR workflows",
        "reason": "Best when you want the same behavior across multiple repos: centralizes the selective-test, retry-once, and failure-report logic while letting each repo supply its own test command mapping."
      },
      {
        "rank": 3,
        "name": "Composite GitHub Action for selective test execution plus summary generation",
        "reason": "Good if you want portable building blocks inside existing workflows; it packages the retry-and-report behavior cleanly, but it is a slightly weaker fit than a full workflow because branch diffing and triggers still need to be wired up outside it."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Perform a security sweep on the Terraform and shell scripts in this repo for unsafe defaults, leaked secrets patterns, and risky permissions, then propose minimal fixes.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Actions + GitHub code scanning with SARIF from Checkov, ShellCheck, and Gitleaks",
        "reason": "Best fit: covers Terraform misconfigurations, shell-script risks, and secret-pattern findings in one GitHub-native workflow, with results centralized in the Security tab and easy PR-based minimal fixes."
      },
      {
        "rank": 2,
        "name": "GitHub secret scanning with push protection and custom patterns",
        "reason": "Best native option for leaked secrets detection and prevention; strong for credential exposure, but incomplete alone because it does not assess Terraform defaults or shell permission risks."
      },
      {
        "rank": 3,
        "name": "GitHub Actions PR gate running terraform validate/fmt and ShellCheck",
        "reason": "Good lightweight baseline: easy to add, low noise, and useful for proposing minimal fixes, but narrower than full security scanning and weaker on secret detection unless combined with a dedicated secret scanner."
      }
    ],
    "documentation_pages": [
      {
        "title": "About code scanning",
        "url": "https://docs.github.com/en/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning",
        "used_for": "Supporting the recommendation to use GitHub code scanning as the central GitHub-native surface for security findings."
      },
      {
        "title": "Uploading a SARIF file to GitHub",
        "url": "https://docs.github.com/en/code-security/code-scanning/integrating-with-code-scanning/uploading-a-sarif-file-to-github",
        "used_for": "Supporting the recommendation to run Terraform and shell scanners in GitHub Actions and publish their results into GitHub code scanning."
      },
      {
        "title": "About secret scanning",
        "url": "https://docs.github.com/en/code-security/secret-scanning/introduction/about-secret-scanning",
        "used_for": "Supporting the recommendation to use GitHub secret scanning for leaked secret patterns."
      },
      {
        "title": "About push protection",
        "url": "https://docs.github.com/en/code-security/secret-scanning/introduction/about-push-protection",
        "used_for": "Supporting the recommendation to prevent new secret leaks at push time."
      }
    ]
  },
  {
    "request": "Prepare a release candidate for this Go service: bump the version, refresh release notes from recent commits, verify the build, and create a checklist of anything blocking the release.",
    "options": [
      {
        "rank": 1,
        "name": "Release Please + GitHub Actions",
        "reason": "Best fit for a Go service: automates version bumps and changelog/release PR generation, then GitHub Actions can run go build/test and attach a blocker checklist to the release-candidate PR."
      },
      {
        "rank": 2,
        "name": "Manual-dispatch GitHub Actions workflow with autogenerated GitHub release notes",
        "reason": "Best when you want explicit release-candidate control: one workflow can bump the version, generate notes from recent merged work, verify the build, and publish a clear checklist in the workflow summary or PR."
      },
      {
        "rank": 3,
        "name": "Release Drafter + separate validation workflow",
        "reason": "Strong for continuously refreshed release notes and RC visibility, but weaker than the top two because version bumping usually needs an additional scripted step or PR process."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "Create and maintain a project board summary for this repo by listing stale pull requests, unassigned high-priority issues, and tasks that are blocked waiting on review.",
    "options": [
      {
        "rank": 1,
        "name": "GitHub Projects with custom fields, filtered views, and built-in workflows",
        "reason": "Best fit because it is board-native: track PRs/issues in one project, add fields like Priority and Blocked Reason, and maintain dedicated views for stale PRs, unassigned high-priority issues, and review-blocked work."
      },
      {
        "rank": 2,
        "name": "Scheduled GitHub Actions workflow that refreshes a summary issue or project draft item",
        "reason": "Best when you want one readable summary artifact. A scheduled workflow can query repo PRs/issues, compute the three lists, and keep a single summary item up to date automatically."
      },
      {
        "rank": 3,
        "name": "Saved GitHub searches linked from the project board",
        "reason": "Lightest-weight option if setup speed matters. Saved searches for stale PRs, unassigned high-priority issues, and review-blocked tasks are easy to maintain, but they are less board-centric and less summary-oriented than Projects or Actions."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "In this Java/Spring app, automate monthly maintenance by checking dependency advisories, identifying deprecated APIs we still use, and opening follow-up tasks with estimates.",
    "options": [
      {
        "rank": 1,
        "name": "Scheduled GitHub Actions workflow that combines Dependabot alerts, a deprecation-warning build, and automatic issue creation",
        "reason": "Best fit because one monthly workflow can pull dependency advisories from Dependabot, run Maven/Gradle with deprecation warnings enabled to find still-used deprecated APIs, and open labeled GitHub issues with size estimates in the body or project fields."
      },
      {
        "rank": 2,
        "name": "Dependabot alerts and security/version updates plus a monthly Actions triage job",
        "reason": "Strong GitHub-native option for dependency maintenance: Dependabot continuously tracks advisories and can raise PRs, while a scheduled Actions job can summarize open alerts, check deprecation output, and create follow-up tasks only when work remains."
      },
      {
        "rank": 3,
        "name": "GitHub code scanning with custom Java analysis plus monthly issue/project automation",
        "reason": "Best when you already use GitHub Advanced Security and want findings managed like security/code quality results; pair code scanning for deprecated API detection with Dependabot for advisories, then automate issue creation and estimates from workflow logic."
      }
    ],
    "documentation_pages": []
  },
  {
    "request": "I’m new to this Rust codebase—please automate a newcomer-friendly status report that explains what changed this week, which tests are failing, and what I should work on next.",
    "options": [
      {
        "rank": 1,
        "name": "Scheduled GitHub Actions workflow that posts a weekly report",
        "reason": "Best fit: fully native automation. A scheduled workflow can collect merged PRs from the last 7 days, detect failing workflow runs/tests, and publish a plain-English markdown report as an issue, discussion, or job summary with a clear 'next tasks' section."
      },
      {
        "rank": 2,
        "name": "GitHub Actions workflow with a Copilot-generated summary",
        "reason": "Best when you want the report to feel newcomer-friendly instead of raw. Use Actions to gather GitHub data, then let Copilot turn it into a concise explanation of changes, failing tests, and recommended next work."
      },
      {
        "rank": 3,
        "name": "GitHub Project board plus an Actions-generated status digest",
        "reason": "Best if you also want prioritization. Actions can summarize weekly changes and failures, while a GitHub Project provides the 'what should I work on next' source of truth using labels, status fields, and good-first issues."
      }
    ],
    "documentation_pages": []
  }
]