[github-docs-seo] Improve Agentic Workflows discoverability for repository automation

{
  "request_count": 10,
  "requests": [
    "Every weekday morning, review new bug reports and pull requests, group duplicates, label them by severity and component, and post a concise triage summary.",
    "Once a week, check our Node.js dependencies for outdated or vulnerable packages, update safe patch and minor versions, run the test suite, and open a pull request with the results.",
    "At the end of each month, generate a report of merged changes, closed issues, deployment frequency, and outstanding work, then save it as a Markdown file in the project reports directory.",
    "Whenever public APIs or CLI commands change, update the relevant README and reference documentation, verify all examples, and open a documentation pull request.",
    "Every night, run the full Python test suite with coverage, compare coverage against the previous run, and create an issue if coverage drops by more than two percentage points.",
    "On the first day of each month, scan the repository and its container configuration for common security misconfigurations, summarize actionable findings, and create prioritized remediation issues.",
    "Before each planned release, verify the changelog, version numbers, migration notes, and release checklist, run the required builds and tests, and report anything missing.",
    "Every Monday, review project issues and milestones for stale assignments, blocked work, and overdue tasks, then post a prioritized planning summary for the team.",
    "After each successful production deployment, collect the deployment status, error-rate, and latency metrics for the next hour and create an incident ticket if any agreed threshold is exceeded.",
    "For every merged feature, identify missing unit or integration tests, add a short test plan to the issue, and flag high-risk areas that need manual verification."
  ],
  "evaluations": [
    {
      "request": "Every weekday morning, review new bug reports and pull requests, group duplicates, label them by severity and component, and post a concise triage summary.",
      "options": [
        {
          "rank": 1,
          "name": "Scheduled GitHub Actions workflow",
          "reason": "Best fit for weekday automation using cron, GitHub APIs, labels, duplicate detection, and a posted issue or discussion summary."
        },
        {
          "rank": 2,
          "name": "GitHub Agentic Workflow",
          "reason": "Well suited to recurring, repository-aware triage that can interpret reports, identify duplicates, apply labels, and summarize results."
        },
        {
          "rank": 3,
          "name": "GitHub App with scheduled processing",
          "reason": "Provides the most control for scalable triage, custom duplicate matching, permissions, and integrations across repositories."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "Once a week, check our Node.js dependencies for outdated or vulnerable packages, update safe patch and minor versions, run the test suite, and open a pull request with the results.",
      "options": [
        {
          "rank": 1,
          "name": "Dependabot version and security updates",
          "reason": "Best fit: schedule weekly checks, group patch/minor updates, detect vulnerabilities, and open pull requests automatically; repository CI can validate each PR."
        },
        {
          "rank": 2,
          "name": "Scheduled GitHub Actions workflow",
          "reason": "Provides full control over npm outdated/audit checks, safe-version filtering, test execution, and pull-request creation in one weekly workflow."
        },
        {
          "rank": 3,
          "name": "Dependabot with grouped updates and required CI checks",
          "reason": "A lower-maintenance hybrid that batches compatible updates while using branch protection and Actions tests to ensure only passing updates merge."
        }
      ],
      "documentation_pages": [
        {
          "title": "Configuring Dependabot version updates",
          "url": "https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuring-dependabot-version-updates",
          "used_for": "Dependabot scheduling, update configuration, and pull-request behavior"
        },
        {
          "title": "Configuring Dependabot security updates",
          "url": "https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates",
          "used_for": "Automated vulnerability-driven dependency updates"
        },
        {
          "title": "Events that trigger workflows",
          "url": "https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows",
          "used_for": "Weekly scheduled GitHub Actions workflows"
        }
      ]
    },
    {
      "request": "At the end of each month, generate a report of merged changes, closed issues, deployment frequency, and outstanding work, then save it as a Markdown file in the project reports directory.",
      "options": [
        {
          "rank": 1,
          "name": "Scheduled GitHub Actions workflow",
          "reason": "Best fit: run monthly, query GitHub data with gh/API, generate Markdown, and commit it directly to the reports directory."
        },
        {
          "rank": 2,
          "name": "GitHub Actions with a custom reporting script",
          "reason": "Ideal when calculations such as deployment frequency and outstanding-work grouping require custom logic and reusable tests."
        },
        {
          "rank": 3,
          "name": "GitHub App or external scheduler using GitHub APIs",
          "reason": "Suitable for organization-wide reporting across repositories, though it requires more infrastructure and credential management."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "Whenever public APIs or CLI commands change, update the relevant README and reference documentation, verify all examples, and open a documentation pull request.",
      "options": [
        {
          "rank": 1,
          "name": "GitHub Actions documentation workflow",
          "reason": "Automatically detect API or CLI changes, validate examples, update documentation, and open a pull request."
        },
        {
          "rank": 2,
          "name": "GitHub Copilot coding agent",
          "reason": "Assign documentation updates and example verification to an agent that can create a pull request."
        },
        {
          "rank": 3,
          "name": "GitHub CLI automation script",
          "reason": "Provide explicit, reviewable commands to detect changes, run checks, generate documentation edits, and open a pull request."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "Every night, run the full Python test suite with coverage, compare coverage against the previous run, and create an issue if coverage drops by more than two percentage points.",
      "options": [
        {
          "rank": 1,
          "name": "Scheduled GitHub Actions workflow",
          "reason": "Use a nightly cron job, coverage.py, persisted artifacts, and the GitHub CLI to compare results and open an issue automatically."
        },
        {
          "rank": 2,
          "name": "Scheduled GitHub Actions workflow with a reusable coverage script",
          "reason": "Centralizes comparison and issue-creation logic in version-controlled Python code, making the nightly process testable and maintainable."
        },
        {
          "rank": 3,
          "name": "Scheduled GitHub Actions workflow with a coverage service",
          "reason": "A service such as Codecov provides historical coverage tracking, while Actions handles the two-point threshold check and issue creation."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "On the first day of each month, scan the repository and its container configuration for common security misconfigurations, summarize actionable findings, and create prioritized remediation issues.",
      "options": [
        {
          "rank": 1,
          "name": "Scheduled GitHub Agentic Workflow",
          "reason": "Best fit for repository-wide and container-configuration review, actionable summaries, prioritization, and automatic issue creation on a monthly schedule."
        },
        {
          "rank": 2,
          "name": "Scheduled GitHub Actions security pipeline",
          "reason": "Run CodeQL plus container/IaC scanners on the first day monthly, upload SARIF results, summarize findings, and create deduplicated prioritized issues."
        },
        {
          "rank": 3,
          "name": "GitHub Advanced Security with scheduled issue automation",
          "reason": "Combines native code scanning, secret scanning, dependency analysis, and Dependabot with a scheduled workflow that turns findings into remediation issues."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "Before each planned release, verify the changelog, version numbers, migration notes, and release checklist, run the required builds and tests, and report anything missing.",
      "options": [
        {
          "rank": 1,
          "name": "GitHub Actions release-readiness workflow",
          "reason": "Automates file and version checks, migration-note validation, builds, tests, and a concise missing-items report before release."
        },
        {
          "rank": 2,
          "name": "Reusable GitHub Actions workflow",
          "reason": "Centralizes release validation so multiple repositories or release branches use the same checklist and test requirements."
        },
        {
          "rank": 3,
          "name": "Pull request release gate with GitHub Actions",
          "reason": "Runs validation whenever a release PR changes, preventing approval or merge until required documentation, builds, and tests are complete."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "Every Monday, review project issues and milestones for stale assignments, blocked work, and overdue tasks, then post a prioritized planning summary for the team.",
      "options": [
        {
          "rank": 1,
          "name": "Scheduled GitHub Actions workflow",
          "reason": "Runs every Monday, queries issues and project data with GitHub CLI/API, and posts a prioritized summary automatically."
        },
        {
          "rank": 2,
          "name": "GitHub Projects views and built-in automations",
          "reason": "Provides visual filtering for stale, blocked, and overdue work, with automations for status and date-based tracking."
        },
        {
          "rank": 3,
          "name": "GitHub Copilot coding agent or custom GitHub App",
          "reason": "Can perform richer analysis and produce team-ready summaries, while a scheduled trigger or external scheduler handles weekly execution."
        }
      ],
      "documentation_pages": []
    },
    {
      "request": "After each successful production deployment, collect the deployment status, error-rate, and latency metrics for the next hour and create an incident ticket if any agreed threshold is exceeded.",
      "options": [
        {
          "rank": 1,
          "name": "GitHub Actions post-deployment monitoring workflow",
          "reason": "Trigger on successful deployment status, poll observability APIs for one hour, evaluate thresholds, and create a GitHub issue automatically."
        },
        {
          "rank": 2,
          "name": "GitHub App or webhook-driven monitor",
          "reason": "Receive deployment_status webhooks, start durable monitoring externally, and open an incident issue through GitHub’s Issues API when thresholds are breached."
        },
        {
          "rank": 3,
          "name": "GitHub Actions reusable workflow with scheduled checks",
          "reason": "Standardize monitoring across repositories using reusable workflows and scheduled executions, while centralizing threshold evaluation and incident creation."
        }
      ],
      "documentation_pages": [
        {
          "title": "Events that trigger workflows",
          "url": "https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows",
          "used_for": "Deployment-status and scheduled GitHub Actions workflow triggers."
        },
        {
          "title": "Webhook events and payloads",
          "url": "https://docs.github.com/en/webhooks/webhook-events-and-payloads#deployment_status",
          "used_for": "Deployment-status webhook handling."
        },
        {
          "title": "REST API endpoints for issues",
          "url": "https://docs.github.com/en/rest/issues/issues#create-an-issue",
          "used_for": "Creating incident tickets as GitHub issues."
        }
      ]
    },
    {
      "request": "For every merged feature, identify missing unit or integration tests, add a short test plan to the issue, and flag high-risk areas that need manual verification.",
      "options": [
        {
          "rank": 1,
          "name": "GitHub Actions workflow with issue and pull request automation",
          "reason": "Runs after merges, analyzes changed features and test coverage, then comments on or updates the associated issue with a test plan and manual-verification risks."
        },
        {
          "rank": 2,
          "name": "GitHub Copilot coding agent assigned from an issue template",
          "reason": "A standardized issue can ask Copilot to review each merged feature, identify missing tests, draft the test plan, and highlight high-risk behavior for human review."
        },
        {
          "rank": 3,
          "name": "GitHub Projects automation with recurring quality-review issues",
          "reason": "Tracks merged features as work items and routes them through a repeatable test-gap and manual-verification checklist, with results recorded in issues."
        }
      ],
      "documentation_pages": []
    }
  ]
}