Skip to main content

fix-release-please

Fix bugs in the forked release-please ecosystem (okou-ai/release-please + okou-ai/release-please-action)

소스 정보

저장소
okou-ai/team-skills
최근 소스 활동
2026년 9월 20일 07:57
감지된 SKILL.md 언어
영어
스타
1
포크
2

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
fix-release-please
description
Fix bugs in the forked release-please ecosystem (okou-ai/release-please + okou-ai/release-please-action)
context
fork
Fix a bug in the project's forked release-please core library, then rebuild the GitHub Action. ## Background | Repo | Fork of | Branch | Role | |------|---------|--------|------| | `okou-ai/release-please` | `googleapis/release-please` | `vm0` | Core library (TypeScript/Node) | | `okou-ai/release-please-action` | `googleapis/release-please-action` | `vm0` | GitHub Action wrapping the core library | - `.github/workflows/release-please.yml` uses `okou-ai/release-please-action@vm0` - The action's `package.json` has `"release-please": "github:okou-ai/release-please#vm0"` - Bugs are almost always in the core library, not the action ## Args Your args are: `$ARGUMENTS` Parse the args to understand what bug to fix. If no args provided, ask the user what the issue is. ## Workflow ### Step 1: Clone both repos ```bash cd /tmp && rm -rf release-please release-please-action git clone https://github.com/okou-ai/release-please.git git clone https://github.com/okou-ai/release-please-action.git cd /tmp/release-please && git config user.email "noreply@vm0.ai" && git config user.name "okou-ai" cd /tmp/release-please-action && git config user.email "noreply@vm0.ai" && git config user.name "okou-ai" ``` ### Step 2: Fix in release-please core Create a fix branch from `main`, make the fix, then cherry-pick to `vm0`: ```bash cd /tmp/release-please git checkout main git checkout -b fix/<description> # ... make the fix, write tests to verify, commit ... git push origin fix/<description> git checkout vm0 git cherry-pick <commit-sha> git push origin vm0 ``` ### Step 3: Rebuild release-please-action This step is **always required** after any core library change: ```bash cd /tmp/release-please-action git checkout vm0 npm install npm run build git add package-lock.json dist/index.js git commit -m "fix: <same description as the core fix>" git push origin vm0 ``` ### Step 4: Verify ```bash cd /tmp/release-please && git log --oneline vm0 -5 cd /tmp/release-please-action && git log --oneline vm0 -5 ``` Report what was changed. ## Syncing upstream If the user asks to sync with upstream: ```bash cd /tmp/release-please git remote add upstream https://github.com/googleapis/release-please.git git fetch upstream git checkout vm0 git rebase upstream/main # Resolve conflicts if any git push origin vm0 --force-with-lease ``` Then rebuild the action (Step 3).
GitHub에서 보기