Skip to content

chore: update repo-platform template to staging@e9b3b64615ad - #57

Closed
Vivswan wants to merge 1 commit into
mainfrom
automation/repo-platform-staging
Closed

chore: update repo-platform template to staging@e9b3b64615ad#57
Vivswan wants to merge 1 commit into
mainfrom
automation/repo-platform-staging

Conversation

@Vivswan

@Vivswan Vivswan commented Aug 24, 2026

Copy link
Copy Markdown
Owner

Automated template update from Vivswan/repo-platform (staging channel).

  • Previous: 268ab14
  • New: staging@e9b3b64615ad

Review any merge conflicts and confirm repository-local sections were preserved before merging.

Note

This branch is regenerated on every sync run; manual commits
pushed to it are overwritten. Make fixes in a separate branch or
after merging.

Copilot AI lite review requested due to automatic review settings August 24, 2026 09:21
@Vivswan
Vivswan enabled auto-merge (squash) August 24, 2026 09:21
@Vivswan
Vivswan disabled auto-merge August 24, 2026 09:23
@Vivswan

Vivswan commented Aug 24, 2026

Copy link
Copy Markdown
Owner Author

Parked deliberately: repo-platform is mid-churn, so this render is stale. The repo-side compliance (the update-release-pr.yml starter hosting the boundary anchor) lands directly; the next sync run will regenerate this PR from a settled template.

@Vivswan Vivswan closed this Aug 24, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The new update-release-pr.yml workflow’s token usage is inconsistent with its documented behavior and should be aligned before merging.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Automated repo-platform template sync to staging@e9b3b64615ad, primarily refreshing managed-file headers/markers and extending the release pipeline with a repo-owned hook that can update the release PR when release-please creates or refreshes it.

Changes:

  • Refresh managed-file notices/markers across policy/docs and config files.
  • Add a repo-owned update-release-pr reusable workflow and wire it into the managed release pipeline.
  • Update copier metadata to track the new template commit.
File summaries
File Description
SECURITY.md Updates the managed/local-section boundary notice text.
LICENSE.md Updates the managed/local-section boundary notice text.
CODE_OF_CONDUCT.md Adds a managed-file header note.
AGENTS.md Clarifies managed vs repo-local guidance and updates repo-owned “escape hatches” list.
.yamllint Adds managed-file header note.
.typography-allow Refreshes managed-file header wording for typography exemptions list.
.github/workflows/update-release-pr.yml Introduces a repo-owned hook workflow for release-PR refresh actions.
.github/workflows/release.yml Wires update-release-pr.yml into the release pipeline and exposes PR metadata outputs.
.gitattributes Adds a brief template baseline header.
.editorconfig Adds managed-file header note.
.copier-answers.yml Bumps tracked template commit to e9b3b64.
Review details

Suppressed comments (1)

.github/workflows/update-release-pr.yml:40

  • GH_TOKEN is currently set to github.token even though this workflow is invoked with secrets: inherit and the header calls out REPO_PLATFORM_TOKEN as the way to ensure follow-up pushes re-trigger CI. Using the same fallback expression as release.yml keeps behavior consistent.
        env:
          GH_TOKEN: ${{ github.token }}
          PR_NUMBER: ${{ inputs.pr_number }}
          HEAD_BRANCH: ${{ inputs.head_branch }}
  • Files reviewed: 11/11 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines +33 to +36
- uses: actions/checkout@v7
with:
ref: ${{ inputs.head_branch }}
- name: Update the release PR
@Vivswan
Vivswan deleted the automation/repo-platform-staging branch August 24, 2026 09:27
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