Repository navigation
Style releases
Use git-release-style.sh for a phpBB style. Committed root style.cfg must contain name and style_version. The sample archive ExampleStyle_1.0.0.zip contains the top folder ExampleStyle/. Metadata and files come from local HEAD by default, or the pinned GitHub default-branch commit with --remote.
cd /path/to/style
git-release-style.sh --create
unzip -l ../git-exported/ExampleStyle_1.0.0.zip
git-release-style.sh --create --remote --output /path/to/packages
git-release-style.sh --release --remote --dry-runAfter testing the package and reviewing the preview, publish explicitly:
git-release-style.sh --release --remoteFor an intentional replacement of an existing version:
git-release-style.sh --release --remote --force --dry-run
git-release-style.sh --release --remote --forceOmit --remote to publish local HEAD; tracked files must be clean and HEAD already pushed. Use --remote --repo OWNER/REPO to select another repository without checking it out. Relative custom output directories are resolved from the current repository root, or the invocation directory outside a checkout.
See all shared options and aliases, remote source selection, and publication rules/recovery. --gh-release remains a publishing alias. Archive layout and export-ignore behavior are unchanged; packaging does not run the project's tests.
- Home
- Installation
- Release workflows
- Extension releases
- Style releases
- Language pack releases
- Default branch releases
- GitHub releases and recovery
- Test board setup
- Smoke and feature checks
- Unit tests and PHP lint
- Screenshots
- Rename upgrade checks
- Template accessibility
- Forum update posts
- Waiting for PR checks
- Troubleshooting
- Maintainer checks