Document branching/release workflow; update local setup to Altis#644
Open
svandragt wants to merge 5 commits into
Open
Document branching/release workflow; update local setup to Altis#644svandragt wants to merge 5 commits into
svandragt wants to merge 5 commits into
Conversation
CONTRIBUTING didn't describe how releases are built, which led to source changes being PR'd straight into the generated release branch (a no-op, since the build Action only runs on main). Add a "Branching and releases" section: work on main, never touch release, the Action builds and force-pushes it, and consumers pin a release commit the Action produced. Also replace the stale Chassis local-setup with Altis Local Server, which is what we actually use now. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
kadamwhite
reviewed
Jun 1, 2026
kadamwhite
left a comment
kadamwhite
left a comment
Contributor
There was a problem hiding this comment.
@svandragt Suggested some pieces that make it more comprehensible to me personally
Sephsekla
reviewed
Jun 1, 2026
Co-authored-by: K Adam White <kadamwhite@users.noreply.github.com>
Co-authored-by: Joe Bailey-Roberts <33831317+Sephsekla@users.noreply.github.com>
Co-authored-by: K Adam White <kadamwhite@users.noreply.github.com>
Co-authored-by: Joe Bailey-Roberts <33831317+Sephsekla@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CONTRIBUTING didn't say anything about how releases are built, and that gap caught me out: I put a source fix straight into the
releasebranch, which does nothing useful, becausereleaseis rebuilt by a GitHub Action on every push tomain– merging intoreleaseskips the build, so the shipped bundle just stays stale.So this adds a "Branching and releases" section that spells that out:
main; branch off it, PR back into it.release– it's generated, and a hand-made commit there is overwritten by the next rebuild.release's source tomain, builds, force-adds the gitignoredbuild/, and force-pushes.releasecommit the Action produced, not a hand-made one.While I was in there I also replaced the Chassis reference in local setup with Altis Local Server, which is what we actually use now. I left the
@rmccuekeys note and the Node 12 build reference alone, and I didn't documentdevelop, since it's effectivelymain-only these days.🤖 Generated with Claude Code