Repository navigation
Default branch releases
Add --remote to any of the three package scripts. Each uses GitHub's configured default branch, pins its commit, and fetches only that snapshot into a temporary Git repository. The caller's branch and working tree stay unchanged.
git-extensions.sh --create --remote --repo OWNER/EXTENSION
git-release-style.sh --create --remote --repo OWNER/STYLE
git-release-langpack.sh --create --remote --repo OWNER/LANGUAGE --check --version 3.3.17--create builds a ZIP without looking for existing releases or generating notes. Package names and layouts follow the package type; metadata and any language validation use the exact same pinned commit. A change to the default branch after resolution does not change that invocation's archive.
git-extensions.sh --release --remote --dry-run --repo phpbbmodders/phpbb-ext-wiki
git-extensions.sh --release --remote --repo phpbbmodders/phpbb-ext-wikiThe first command builds/replaces the local ZIP and previews generated notes without changing a GitHub tag, release, or asset. The second publishes it. Substitute the style or language-pack script as appropriate, retaining language validation options when needed. Preview and publication are separate invocations, so review their printed commits.
Use --output DIR for a custom destination. The default is ../git-exported from the repository root, or from the invocation directory outside a checkout. Relative custom directories use that same base.
Existing non-dev versions require explicit --force for replacement; it cannot bypass GitHub protections. See all shared options and publication/recovery.
The separate API entry point is retired. Its remote functionality is now in git-extensions.sh and is also available for styles and language packs.
| Old command | New command |
|---|---|
git-release-api.sh --dry-run |
git-extensions.sh --release --remote --dry-run |
git-release-api.sh --release |
git-extensions.sh --release --remote |
Keep any existing --repo OWNER/REPO and --output DIR arguments. Update aliases, symlinks, and automation that still invoke the retired entry point. Do not copy old standalone script files over the updated checkout.
- 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