Skip to content

Add tracking doc for the Private Actions / Execution Policies stack - #39044

Draft
irving-santiago wants to merge 1 commit into
masterfrom
irving.santiago/private-actions-execution-policies-docs
Draft

Add tracking doc for the Private Actions / Execution Policies stack#39044
irving-santiago wants to merge 1 commit into
masterfrom
irving.santiago/private-actions-execution-policies-docs

Conversation

@irving-santiago

@irving-santiago irving-santiago commented Aug 10, 2026

Copy link
Copy Markdown

What does this PR do? What is the motivation?

This is the integration branch for a 10-PR stack that adds and rewrites the Private Actions documentation to cover Execution Policies, a new authorization model for private action runners running in the Datadog Agent.

Each slice PR below targets this branch, so each is independently reviewable. This branch itself will merge into master in a single rollup PR after all 10 slices are reviewed and merged into it.

Merge readiness

  • Ready for merge

For Datadog employees:

  • ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
  • 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Claude Code carried a pre-drafted, human-authored content plan into this repo across all 10 slices, running Vale and fixing issues along the way.

Additional notes

@datadog-prod-us1-4

Copy link
Copy Markdown
Contributor

Pipelines

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/documentation | build_preview   View in Datadog   GitLab

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 91196f4 | Docs | Datadog PR Page | Give us feedback!

@estherk15 estherk15 self-assigned this Aug 10, 2026
@estherk15 estherk15 added the WORK IN PROGRESS No review needed, it's a wip ;) label Aug 10, 2026
@jhgilbert jhgilbert added the astro-reorg-no-conflicts Needs manual conflict resolution after replatforming reorg label Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

astro-reorg-no-conflicts Needs manual conflict resolution after replatforming reorg WORK IN PROGRESS No review needed, it's a wip ;)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants