Skip to content

Notify openocean-build of each push to 3.0 - #480

Merged
tsaubergine merged 1 commit into
3.0from
add-notify-openocean-build/3.0
Nov 13, 2026
Merged

tsaubergine merged 1 commit into
3.0from
add-notify-openocean-build/3.0

Conversation

@tsaubergine

Copy link
Copy Markdown
Member

This adds .github/workflows/notify-openocean-build.yml, a copy of DCCL's for branch 3.0 and project goby3. On each push to 3.0, it starts openocean-build's continuous.yml. That packages the new head for the continuous apt channel within minutes, rather than at openocean-build's next 6-hourly poll (openocean-software/openocean-build#44).

  • What it can do. The token comes from openocean-build's dispatch GitHub App, whose only permission is Actions: write on openocean-build. The workflow only names the project; openocean-build looks up and verifies the new head itself, so a misused token can at most start a check.
  • Credentials. The App's ID and private key are this repository's OOS_DISPATCH_APP_ID variable and OOS_DISPATCH_APP_KEY secret. This repository has its own key, so it can be revoked without affecting DCCL's.
  • This pull request's check. A pull request that changes the workflow only checks that the token can see continuous.yml. Fork pull requests are skipped, since they don't get the credentials.

No release note, as nothing user-visible changes.


Generated by Claude Code

openocean-build packages each new head of 3.0 for its continuous apt
channel. This starts that build within minutes of a push, rather than at
openocean-build's next 6-hourly poll.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_01TCmHEtFYqHoQ7FSkAsKLKz
@tsaubergine
tsaubergine merged commit 0ffe697 into 3.0 Nov 13, 2026
5 of 10 checks passed
@tsaubergine
tsaubergine deleted the add-notify-openocean-build/3.0 branch November 13, 2026 04:37
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