mirror of
https://github.com/linear/linear-release.git
synced 2026-09-14 20:00:10 +08:00
b89cd41f61
* Reorganize examples into folders with READMEs Move each CI example into its own directory with a platform-conventional filename and a README explaining when to use it, how it works, and setup steps. Update SKILL.md links to point to the new folder paths. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Fix inaccurate customization guidance in READMEs - GitLab CI continuous: clarify that $CI_DEFAULT_BRANCH is a predefined variable and show how to replace it in the rule expression - GitHub Actions scheduled: note that branch pattern changes must also update startsWith() guards and version derivation in the workflow Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Rework docs * Rename example files to platform conventions Use the filename each CI platform expects: `linear-release.yml` for GitHub Actions workflows, `config.yml` for CircleCI, `.gitlab-ci.yml` for GitLab CI. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
23 lines
1.0 KiB
Markdown
23 lines
1.0 KiB
Markdown
# GitHub Actions — Continuous Pipeline
|
|
|
|
Every deployment creates a completed release automatically.
|
|
|
|
## When to use
|
|
|
|
Use this when your team ships continuously — every push to main is a deploy, and each deploy should be tracked as its own release in Linear.
|
|
|
|
## How it works
|
|
|
|
On every push to `main`, the workflow runs `sync` via the official [Linear Release Action](https://github.com/linear/linear-release-action). This creates a new release from the commits since the last release and immediately marks it as complete.
|
|
|
|
## Setup
|
|
|
|
1. Create a release pipeline in Linear (Settings → Releases) and grab the access key.
|
|
2. Add `LINEAR_ACCESS_KEY` as a repository secret (Settings → Secrets and variables → Actions → New repository secret).
|
|
3. Copy [`linear-release.yml`](linear-release.yml) into `.github/workflows/`.
|
|
|
|
## Customization
|
|
|
|
- **Branch name**: Change `main` in the `branches` filter if your default branch is different.
|
|
- **Monorepo path filters**: Add the `include_paths` input to scope the release to specific directories.
|