Skip to content

ci: verify what we publish from the consumer side (#5) #61

ci: verify what we publish from the consumer side (#5)

ci: verify what we publish from the consumer side (#5) #61

Workflow file for this run

# Calls the canonical plugin-ci reusable workflow (GetBusbar/busbar/.github/workflows/plugin-ci.yml)
# instead of hand-copying build/test/signoff steps here — see that file for what actually runs.
name: ci
on:
push:
branches: [main, dev, qa]
pull_request:
branches: [main, dev, qa]
# Manual trigger. Needed because `gh run rerun` PINS the reusable-workflow SHA:
# a rerun re-uses the plugin-ci.yml snapshot from the original run, so a fix landing in
# core's reusable workflow can only be picked up by a NEW run, never by rerunning an old one.
workflow_dispatch: {}
jobs:
ci:
uses: GetBusbar/busbar/.github/workflows/plugin-ci.yml@dev
with:
plugin_crate: busbar-store-postgres-plugin
plugin_kind: store
plugin_alias: postgres
service: postgres
busbar_ref: ${{ github.base_ref || github.ref_name }}
# base_ref FIRST: on a pull_request `github.ref_name` is '<number>/merge', not a branch
# name, so this asked busbar for a branch called '5/merge' and the sibling checkout died
# with an unreadable git error on EVERY pull request to this repo.
# NOTE: no extra_sibling_test_command here (unlike before this repo's 2-crate-workspace
# restructure). `extra_sibling_test_command: cargo test -p busbar-store-postgres` used to
# exercise the monorepo's own copy of the store logic against the sibling busbarAI checkout's
# `crates/store-postgres` package; that package no longer exists in busbarAI (the real logic
# crate now lives HERE, in this repo's own `store-postgres/` member) — the plugin's own
# `cargo test` step above (working-directory: plugin, a workspace covering both
# `busbar-store-postgres` and `busbar-store-postgres-plugin`) already exercises it in full,
# so the sibling-checkout step would now fail (no such package) and is redundant besides.