Add tracking doc for the Private Actions / Execution Policies stack - #39044
Draft
irving-santiago wants to merge 1 commit into
Draft
Add tracking doc for the Private Actions / Execution Policies stack#39044irving-santiago wants to merge 1 commit into
irving-santiago wants to merge 1 commit into
Conversation
Author
This was referenced Aug 10, 2026
Contributor
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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
masterin a single rollup PR after all 10 slices are reviewed and merged into it.Merge readiness
For Datadog employees:
<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./reviewto 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