Skip to content

Add the caller that adopts an EnergyPlus release - #21

Open
samuelduchesne wants to merge 2 commits into
mainfrom
adopt-energyplus
Open

samuelduchesne wants to merge 2 commits into
mainfrom
adopt-energyplus

Conversation

@samuelduchesne

@samuelduchesne samuelduchesne commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

1. Change

Adds .github/workflows/adopt-energyplus.yml, the caller of the reusable adoption workflow in idfkit-conformance at governance-2026.24. It is dispatched with one input, the EnergyPlus release, and proposes that release as a pull request on energyplus/X.Y.Z.

The caller holds no logic. The steps of this project, their commands and its gate are declared in governance/energyplus.toml of idfkit-conformance. For this project every step is automated, so the pull request opens ready for review, not as a draft. The run never merges, publishes, releases or deploys.

2. Behaviour in this project

The delivery pins in .mcp.json and .lsp.json are not moved here. A run reports that it is waiting until both servers are pinned at versions that carry the release, and then rewrites the 2 declared statements.

Open point: bump-idfkit.yml moves only .mcp.json. Nothing moves .lsp.json, so the step waits on a person.

3. Verification

The caller passes the conformance check of callers (one call, a governance tag stated identically on uses: and as the input, the run name, no publishing permission). It has not run on GitHub: a workflow can be dispatched only once it is on the default branch.

The caller holds no logic. The steps, their commands and the gate are
declared for this project in governance/energyplus.toml of
idfkit-conformance, read at governance-2026.24.
Two dispatches for one release ran in parallel and each regenerated and
pushed the branch energyplus/X.Y.Z. A concurrency group keyed on the
release makes the second run wait for the first, as bump-idfkit.yml does.

The header named bump-idfkit.yml as the mover of the idfkit-mcp pin and
was silent on .lsp.json. No workflow moves that pin, so the waiting
state clears only when a maintainer edits it. The header now says so.
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.

1 participant