Add sender sync workflow for shared OpenAPI artifacts

Open
  • Is something wrong?
#44 0 comments 1 reaction 2 assignees View on GitHub

@cubap is already working on this.

Since May 9, 2026.

  • #45 by @copilot-swe-agent — closed without merging

Assessment

This issue has not been assessed yet.

Description

Implement the sender side of the shared OpenAPI artifact sync so TinyPen can own and export its canonical contract artifact from its own repository, then notify cubap/rerum_openapi for a sync PR.

Scope:

  • Add a sender workflow in TinyPen
  • Treat the TinyPen repo as the editing surface for the canonical shared artifact
  • Sync into the matching receiver artifact under cubap/rerum_openapi
  • Keep the receiver-side target file stubbed there so sync updates an existing artifact rather than creating it on first run

Suggested provider source path:

  • openapi/components/tinypen-shared-components.openapi.yaml

Receiver target:

  • schemas/openapi/tinypen-shared-components.openapi.yaml

Acceptance criteria:

  • TinyPen can change one canonical exported artifact and open or update a PR in cubap/rerum_openapi
  • Consumers continue validating against cubap/rerum_openapi without per-feature contract workflows
  • The provider source path follows a standard and discoverable OpenAPI layout
Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CenterForDigitalHumanities/TinyPen

All issues in CenterForDigitalHumanities/TinyPen

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.