Skip to content

Report company upstream drift - #21

Open
roland-at-ailtir wants to merge 9 commits into
paperclipai:mainfrom
Team-Ailtir:main
Open

Report company upstream drift#21
roland-at-ailtir wants to merge 9 commits into
paperclipai:mainfrom
Team-Ailtir:main

Conversation

@roland-at-ailtir

@roland-at-ailtir roland-at-ailtir commented Jun 15, 2026

Copy link
Copy Markdown

Summary

  • replace automated company refresh PR creation with a scheduled/manual upstream drift report
  • keep scripts/refresh-companies report-only: it compares tracked metadata.sources commits with the latest semver-like tag or default-branch HEAD and reports stale sources/new upstream skill paths
  • maintain a single tracking issue titled Company upstream refresh report instead of opening refresh/ branches
  • keep Paperclip package validation separate for maintainer-authored PRs, with manual PR validation still available
  • document the more limited workflow and GitHub Issues/Actions setup in README.md and AGENTS.md
  • update workflow actions to current major versions (actions/checkout@v6, actions/setup-node@v6)

Rationale

Full company refreshes are package-level product decisions: maintainers need to decide which upstream skills belong in a company, which support files to copy, and how agents/docs should change. This PR automates drift awareness and validation, but leaves actual package refreshes to reviewed maintainer PRs.

Validation

Setup Notes

No custom secret is required. The drift workflow uses GITHUB_TOKEN with contents: read and issues: write; GitHub Issues must be enabled for the tracking issue.

@roland-at-ailtir roland-at-ailtir changed the title Automate company skill refreshes Report company upstream drift Jun 15, 2026
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