Skip to content

Auto-push regenerated overview apps on internal PRs - #702

Merged
oblomov-dev merged 1 commit into
standardfrom
claude/job-auf-rot-0dvx40
Aug 4, 2026
Merged

oblomov-dev merged 1 commit into
standardfrom
claude/job-auf-rot-0dvx40

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

Summary

Enhance the generate_overview_apps workflow to automatically regenerate and push overview app catalogs when they're out of date on pull requests from branches within this repository, while maintaining strict verification on fork PRs and pushes to the protected standard branch.

Key Changes

  • Smart checkout: Modified the checkout step to use the PR head branch (instead of merge commit) for internal PRs, enabling commits to be pushed back to the branch
  • Deploy key integration: Added SSH key configuration using the ACTION_KEY_SAMPLES secret to push changes without re-triggering verification issues that would occur with GITHUB_TOKEN
  • Conditional push logic: Implemented conditional behavior that:
    • Automatically regenerates and pushes catalogs on internal PRs when out of date
    • Fails with an error message on fork PRs and standard branch pushes (where pushing isn't possible)
    • Provides clear feedback via notice messages when auto-pushing occurs
  • Updated documentation: Clarified in AGENTS.md that the workflow serves as a safety net, not a substitute for manual regeneration

Implementation Details

  • The workflow now checks if it can push (CAN_PUSH condition) based on event type, repository ownership, and secret availability
  • When catalogs are out of date and pushing is possible, it commits with the bot identity and pushes to the PR branch
  • When pushing isn't possible, it fails with actionable guidance for contributors
  • The approach is safe for fork PRs and before the deploy key is configured—it simply guards and fails on any diff

https://claude.ai/code/session_01Cpu46KEg8yScnPEVUKS8fL

…branch

The overview catalogs are fully derived from the folder tree, but CI only
verified them and failed the pull request when they were stale, so every
contributor had to push a mechanical follow-up commit.

For a pull request from a branch of this repository the workflow now checks
out the head branch, regenerates the catalogs and pushes the result back, so
the pull request goes green on its own. The push uses a deploy key
(ACTION_KEY_SAMPLES, the pattern already used for ACTION_KEY_FRONTEND and
ACTION_KEY_LOCAL) because a push with the default GITHUB_TOKEN would not
re-trigger the other checks and would leave the new commit unverified.

Fork pull requests receive no secrets and standard is protected, so both keep
the previous guard-and-fail behaviour. Until the secret is configured the
workflow behaves exactly as before for every event.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Cpu46KEg8yScnPEVUKS8fL
@oblomov-dev
oblomov-dev merged commit 178ec59 into standard Aug 4, 2026
7 checks passed
@oblomov-dev
oblomov-dev deleted the claude/job-auf-rot-0dvx40 branch August 4, 2026 10:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants