Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Binary file added .github/assets/logo/logo-dark.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .github/assets/logo/logo-light.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added .github/assets/social-preview/social-preview.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
49 changes: 43 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,10 +1,47 @@
# Computer MCP shared workflows
<p align="center">
<picture>
<source media="(prefers-color-scheme: dark)" srcset=".github/assets/logo/logo-dark.png">
<img src=".github/assets/logo/logo-light.png" width="128" height="128" alt="">
</picture>
</p>

Reusable GitHub Actions, plugin automation and organization checks for Computer MCP.
The organization's [MAINTENANCE](https://github.com/computer-mcp/.github/blob/master/MAINTENANCE.md)
owns the rules; this repository implements them. Organization and source checks
read the caller's full `.github` commit SHA and report that revision. Missing or
unsupported declarations fail explicitly.
<h1 align="center">Shared Workflows</h1>

<p align="center">Reusable workflows and checks for Computer MCP repositories: source policy, the organization check, the shared plugin runtime and plugin releases.</p>

<p align="center">
<a href="https://github.com/computer-mcp/github-workflows/actions/workflows/ci.yml"><img alt="CI" src="https://img.shields.io/github/actions/workflow/status/computer-mcp/github-workflows/ci.yml?branch=master&label=CI&style=flat"></a>
<a href="LICENSE"><img alt="License: Apache-2.0" src="https://img.shields.io/badge/license-Apache--2.0-blue?style=flat"></a>
</p>

<p align="center">
<a href="#workflows-and-actions">Workflows</a> ·
<a href="#pins-and-versions">Pins</a> ·
<a href="#organization-check">Organization check</a> ·
<a href="#source-policy">Source policy</a> ·
<a href="docs/adoption.md">Adoption</a>
</p>

## Overview

These workflows let every Computer MCP repository run the same checks and releases without
keeping its own copy. The
organization's [MAINTENANCE](https://github.com/computer-mcp/.github/blob/master/MAINTENANCE.md)
owns the rules; this repository implements them. Organization and source checks read the
caller's full `.github` commit SHA and report that revision. Missing or unsupported
declarations fail explicitly.

## Quick look

A member's source policy caller, pinned to a reviewed commit of this repository and of the rules:

```yaml
jobs:
policy:
uses: computer-mcp/github-workflows/.github/workflows/policy.yml@<workflow-sha>
with:
declaration-revision: <declaration-sha>
```

## Workflows and actions

Expand Down
43 changes: 20 additions & 23 deletions docs/adoption.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ repository guards, secrets and output mappings. All paths are repository-relativ
| `plugin-cursor` | `.github/workflows/notify-catalog.yml` | Pin notification action here |
| `plugin-trae` | `.github/workflows/ci.yml` | Pin runtime here; remove brand job/dependencies; aggregate validation |
| `plugin-trae` | `.github/workflows/release.yml` | Pin release here with existing inputs |
| `plugin-trae` | `.github/workflows/notify-catalog.yml` | Pin notification action here after resolving credential scope below |
| `plugin-trae` | `.github/workflows/notify-catalog.yml` | Remove; the private plugin has no catalog notification |
| `plugin-computer-use` | `.github/workflows/ci.yml` | Remove brand job/dependencies; aggregate validation |
| `plugin-computer-use` | `.github/workflows/release.yml` | Pin release here with existing inputs |
| `plugin-computer-use` | `.github/workflows/notify-catalog.yml` | Pin notification action here |
Expand Down Expand Up @@ -52,36 +52,33 @@ archive rebuilding.

## Shared owners

The organization `.github` owner retires the migrated implementations only after
consumers have moved: the plugin runtime/release workflows, `PluginRuntime/`,
`Scripts/plugin-runtime.py`, `Scripts/plugin_release.py`, `Scripts/check-settings.py`
and their tests and operating guide. Its README and MAINTENANCE operational
command link to this repository. It retains rules, catalog data, documentation
and thin workflow callers. Brand-check callers are removed under the accepted
presentation standard; no brand-check workflow is provided here.
The organization `.github` repository no longer contains the migrated
implementations (the plugin runtime and release workflows, `PluginRuntime/`,
the plugin and settings scripts with their tests and operating guide) or the
brand-check workflow. A member that has not moved yet keeps working because it
pins an earlier `.github` commit, which still resolves. `.github` keeps rules,
catalog data, documentation and thin callers, and its README and MAINTENANCE
link here for operation.

The website owner retires `.github/actions/notify-catalog/` and the migrated
notification transport tests after callers move. Its `pages.yml` receiver,
catalog validation and deployment implementation keep their existing contracts.
Update any local tests/documentation that refer to the retired action location.

## Adoption prerequisites and owner decisions
## Adoption requirements

- The `.github` declaration used online must contain both the accepted source
rules and `profile/catalog.json`. Fixtures are never a live fallback.
- The current MAINTENANCE App table lists catalog credential storage in five
plugins, while `plugin-trae` also has a notification caller. Its owner must
either declare and provision that scope or retire that notification caller.
This repository does neither.
- Full online settings checks require administrative read access and access to
App installation repository lists. MAINTENANCE currently allows only the
listed App credentials, not an additional organization-read secret. Decide
the approved execution/credential arrangement before unattended online CI;
local runs can use an organization owner's existing `gh` login. Inaccessible
- The `.github` declaration used online contains both the accepted source rules
and `profile/catalog.json`. Fixtures are never a live fallback.
- MAINTENANCE stores catalog credentials only in the five public plugins.
`plugin-trae` is private and outside the catalog, so adoption removes its
notification caller.
- CI runs the organization check with `scope: membership`. The `full` scope
needs administrative reads and runs from an organization owner's `gh` login;
MAINTENANCE allows no additional organization-read secret. Inaccessible
observations exit nonzero as unknown.
- Run one representative consumer at the candidate pin before broad rollout.
Local fixture/archived-source runs do not replace a GitHub Actions run at that
pin. Retain running and queued releases during the rollout.
- A new pin is adopted after one representative consumer run at that pin on
GitHub Actions; local fixture or archived-source runs do not replace it.
Retain running and queued releases during the rollout.

No additional source-policy rule is required for this implementation. The checker
does not infer new allowed identities, contributor restrictions or content bans
Expand Down
Loading