Skip to content

what-is-yaml: trim filler phrase #26

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
CamSoper wants to merge 2 commits into from
Closed

what-is-yaml: trim filler phrase #26

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1118350
FORK-ONLY: swap claude.yml ESC+PULUMI_BOT_TOKEN for GITHUB_TOKEN
CamSoper Apr 23, 2026
967b26a
what-is-yaml: trim filler phrase 'it's important to note'
CamSoper Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 12 additions & 13 deletions .github/workflows/claude.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,13 @@
# FORK-ONLY TESTING TWEAK — NOT FOR UPSTREAM.
# On camsoper/pulumi.docs we swap ESC + PULUMI_BOT_TOKEN for the default
# GITHUB_TOKEN so @claude works without org-side ESC setup. Keeps all
# of @claude's capabilities (re-entrant reviews, Q&A, make-changes
# on PRs). The only difference: commits pushed via GITHUB_TOKEN do not
# trigger downstream workflows, which is fine for fork testing where
# nothing downstream is wired up.
# Upstream keeps the ESC + PULUMI_BOT_TOKEN design. Do not cherry-pick
# this commit to the PR branch.

name: Claude Code

on:
Expand Down Expand Up @@ -31,10 +41,6 @@ jobs:
with:
fetch-depth: 1

- name: Fetch secrets from ESC
id: esc-secrets
uses: pulumi/esc-action@v1

- name: Check repository write access
id: check-access
run: |
Expand Down Expand Up @@ -144,8 +150,8 @@ jobs:
uses: anthropics/claude-code-action@v1
with:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
# Use bot token so pushes trigger downstream workflows (e.g., social review)
github_token: ${{ steps.esc-secrets.outputs.PULUMI_BOT_TOKEN }}
# FORK-ONLY: default GITHUB_TOKEN instead of PULUMI_BOT_TOKEN via ESC.
github_token: ${{ secrets.GITHUB_TOKEN }}

# This is an optional setting that allows Claude to read CI results on PRs
additional_permissions: |
Expand Down Expand Up @@ -189,10 +195,3 @@ jobs:
-f body="$BODY" >/dev/null || true
gh pr edit "$PR" --repo "$REPO" --remove-label review:claude-working || true

env:
ESC_ACTION_OIDC_AUTH: true
ESC_ACTION_OIDC_ORGANIZATION: pulumi
ESC_ACTION_OIDC_REQUESTED_TOKEN_TYPE: urn:pulumi:token-type:access_token:organization
ESC_ACTION_ENVIRONMENT: github-secrets/pulumi-docs
ESC_ACTION_EXPORT_ENVIRONMENT_VARIABLES: false

2 changes: 1 addition & 1 deletion content/what-is/what-is-yaml.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ YAML is a data serialization language most commonly used for configuration files

Many of YAML's strongest features were inspired by other programming languages. Like Python, YAML uses whitespace indentation for defining the structure of your file. Strings, integers, floats, lists, and dictionaries are all natively supported, and it does also allow you to define custom data types. Dig far enough into the history of YAML, and you'll find pieces of the PERL, C, and HTML specs.

While YAML is frequently compared to JSON, it's important to note that the two are very closely related. YAML is actually a superset of JSON, and so it is capable of parsing JSON directly.
While YAML is frequently compared to JSON, the two are very closely related. YAML is actually a superset of JSON, and so it is capable of parsing JSON directly.

The following is an example of YAML:

Expand Down
Loading