docs: compare agentic campaigns to GitHub Security Campaigns

[Copilot]

Completed: Compare Agentic Campaigns to GitHub Security Campaigns

• Create comparison documentation in campaigns section
• Document key differences between agentic campaigns and GitHub security campaigns
• Add comparison to astro.config.mjs sidebar
• Add link from campaigns overview page
• Review and finalize content
• Clarify Enterprise Cloud requirement for REST API integration example
• Streamline documentation - remove repetition and bloat

Summary

Created concise comparison documentation between GitHub Agentic Workflows campaigns and GitHub's Security Campaigns feature.

Reduced from 285 to 65 lines (77% reduction) to improve clarity and remove redundancy while maintaining all essential information.

The streamlined document includes:

• Clear opening definitions: Concise descriptions of both campaign types
• Key differences table: Side-by-side comparison of 6 core aspects
• When to use each: Direct guidance on choosing the right tool
• Integration example: Working code example with Enterprise Cloud requirement note
• Feature comparison: Single consolidated table with 7 key differentiators
• Essential links: Curated documentation references

The document follows GitHub Docs voice and Astro Starlight best practices, emphasizing conciseness and clarity.

Custom agent used: technical-doc-writer
AI technical documentation writer for GitHub Actions library using Astro Starlight and GitHub Docs voice

Original prompt

Compare "agentic campaigns" to GitHub campaings: https://docs.github.com/en/enterprise-cloud@latest/code-security/securing-your-organization/fixing-security-alerts-at-scale/about-security-campaigns

Custom agent used: technical-doc-writer
AI technical documentation writer for GitHub Actions library using Astro Starlight and GitHub Docs voice

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[mnkiefer]

@copilot: The following will only work for Enterprise customers?
Create GitHub Security Campaign via REST API for categories with 5+ alerts.

[Copilot]

@copilot: The following will only work for Enterprise customers?
Create GitHub Security Campaign via REST API for categories with 5+ alerts.

Yes, that's correct. The REST API for creating GitHub Security Campaigns requires GitHub Enterprise Cloud. I've added a note in commit 031ddc4 to clarify this requirement in the integration example section.

[mnkiefer]

@copilot: Make sure the newly created docs and concise and clear, do not repeat or bloat.

[Copilot]

@copilot: Make sure the newly created docs and concise and clear, do not repeat or bloat.

Streamlined the documentation in commit 6bb2e8f, reducing from 285 to 65 lines (77% reduction). Removed:

• Redundant overview and use case sections
• Three separate feature tables (merged into one)
• Verbose architecture diagrams
• Duplicate migration/integration content
• Excessive links section

All essential information is retained in a clear, concise format.