Skip to content

Commit faff44b

Browse files
authored
Merge release/1.2.0 into master. Forced merge with PAT token.
Merge release/1.2.0 into master
2 parents 52e63a7 + d0b5a12 commit faff44b

437 files changed

Lines changed: 84721 additions & 136592 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

.agent-sessions/session_1763235331644_8853527.json

Lines changed: 0 additions & 49 deletions
This file was deleted.

.agent-sessions/session_1763235335017_cveqlr8.json

Lines changed: 0 additions & 36 deletions
This file was deleted.

.agent-sessions/session_1763236315499_je0w7pl.json

Lines changed: 0 additions & 49 deletions
This file was deleted.

.agent-sessions/session_1763236327442_argwhxe.json

Lines changed: 0 additions & 36 deletions
This file was deleted.

.cursor/rules/project-context.mdc

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
description: Git Board Flow project context, commands, and conventions
3+
alwaysApply: true
4+
---
5+
6+
# Git Board Flow – Project Context
7+
8+
**Git Board Flow** is a GitHub Action (and local CLI) that automates branch management, GitHub project linking, and issue/PR tracking using Git-Flow. It uses **OpenCode** for all AI features (progress detection, error detection, PR descriptions, copilot).
9+
10+
## Tech stack
11+
12+
- **Runtime**: Node.js 20 (use `nvm use 20` before running commands).
13+
- **Language**: TypeScript.
14+
- **Build**: `@vercel/ncc` bundles the action and CLI into `build/`.
15+
- **Tests**: Jest.
16+
17+
## Commands (run from repo root)
18+
19+
```bash
20+
nvm use 20
21+
npm install
22+
npm run build
23+
npm test
24+
npm run test:watch
25+
npm run test:coverage
26+
npm run lint
27+
npm run lint:fix
28+
```
29+
30+
- **Build**: `npm run build` – compiles `src/actions/github_action.ts` → `build/github_action/`, `src/cli.ts` → `build/cli/`, and sets the CLI as executable.
31+
- **Tests**: `npm test` – runs Jest (exclude e2e when relevant). Use `npm run test:watch` for watch mode, `npm run test:coverage` for coverage.
32+
- **Lint**: `npm run lint` – ESLint + typescript-eslint on `src/` (recommended + unused-vars, no-explicit-any). Use `npm run lint:fix` to auto-fix.
33+
34+
## What to ignore
35+
36+
- **`build/`** – Compiled output (bundled JS, generated .d.ts). Do not edit or rely on it; treat it as generated. Do not run tests or lint against `build/`.
37+
- **`.agent-sessions/`** – Session data; ignore in context unless debugging sessions.
38+
39+
## Key paths
40+
41+
- `src/actions/github_action.ts` – GitHub Action entry; reads inputs and runs the main flow.
42+
- `src/actions/local_action.ts` – CLI entry; same logic with local/config inputs.
43+
- `src/actions/common_action.ts` – Shared flow: single actions vs issue/PR/push pipelines.
44+
- `src/usecase/` – Use cases (issue, pull request, commit, single actions).
45+
- `src/data/model/` – Domain models (Execution, Ai, Issue, etc.).
46+
- `src/data/repository/ai_repository.ts` – OpenCode API (ask, askAgent, copilotMessage); no separate agent layer.
47+
- `action.yml` – Action metadata and input definitions.
48+
49+
## Conventions
50+
51+
- Prefer TypeScript; keep action and CLI buildable with `ncc`.
52+
- Use existing logger (`logInfo`, `logError`, `logDebugInfo`) and constants (`INPUT_KEYS`, `ACTIONS`) instead of ad-hoc strings.
53+
- When adding inputs, update `action.yml`, `INPUT_KEYS` in `src/utils/constants.ts`, and the corresponding read in `github_action.ts` (and optionally `local_action.ts`).

.github/pull_request_template.md

Lines changed: 144 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,144 @@
1+
<!--
2+
Thank you for opening a Pull Request 🚀
3+
Please fill out this template as completely as possible.
4+
Clear PRs = faster reviews = better software.
5+
-->
6+
7+
# 📌 Summary
8+
<!--
9+
Briefly explain what this PR does and why it is needed.
10+
Focus on the intent, not the implementation details.
11+
-->
12+
13+
---
14+
15+
## 🎯 Related Issues / Tickets
16+
<!--
17+
Link any related issues, tickets, or discussions.
18+
Use GitHub keywords to auto-close issues when merged.
19+
-->
20+
- Closes #
21+
- Related to #
22+
23+
---
24+
25+
## 🧩 Scope of Changes
26+
<!--
27+
Describe the scope and nature of the changes at a high level.
28+
-->
29+
- Added:
30+
- Updated:
31+
- Removed:
32+
- Refactored:
33+
34+
---
35+
36+
## 🛠️ Technical Details
37+
<!--
38+
Explain important technical decisions, trade-offs, or architecture changes.
39+
Include anything that may not be obvious from reading the code.
40+
-->
41+
42+
---
43+
44+
## 🔍 How to Test
45+
<!--
46+
Provide clear, step-by-step instructions to test this change.
47+
Assume the reviewer is unfamiliar with the context.
48+
-->
49+
1.
50+
2.
51+
3.
52+
53+
---
54+
55+
## 🧪 Test Coverage
56+
<!--
57+
Indicate what types of tests were added or updated.
58+
-->
59+
- [ ] Unit tests
60+
- [ ] Integration tests
61+
- [ ] End-to-end (E2E) tests
62+
- [ ] Manual testing only (explain why)
63+
64+
---
65+
66+
## 📸 Screenshots / Recordings (UI changes only)
67+
<!--
68+
Include before/after screenshots or short videos if this PR affects the UI.
69+
-->
70+
71+
---
72+
73+
## ⚠️ Breaking Changes
74+
<!--
75+
List any breaking changes and required migration steps.
76+
If none, state "None".
77+
-->
78+
- None
79+
80+
---
81+
82+
## 🚀 Deployment Notes
83+
<!--
84+
Anything required or important during deployment:
85+
- environment variables
86+
- database migrations
87+
- feature flags
88+
- deployment order
89+
-->
90+
- [ ] Requires database migration
91+
- [ ] Requires environment variable changes
92+
- [ ] Requires feature flag toggle
93+
- [ ] No special deployment steps
94+
95+
Details:
96+
97+
---
98+
99+
## 🔒 Security Considerations
100+
<!--
101+
Mention any security-related implications or validations.
102+
-->
103+
- [ ] No security impact
104+
- [ ] Input validation changes
105+
- [ ] Authentication / authorization changes
106+
- [ ] Sensitive data handling changes
107+
108+
---
109+
110+
## 📈 Performance Impact
111+
<!--
112+
Describe any performance considerations, improvements, or regressions.
113+
-->
114+
- [ ] No performance impact
115+
- [ ] Improves performance
116+
- [ ] Potential performance regression (explain)
117+
118+
---
119+
120+
## 📝 Notes for Reviewers
121+
<!--
122+
Highlight areas that need special attention or context for reviewers.
123+
-->
124+
125+
---
126+
127+
## ✅ Checklist
128+
<!--
129+
Confirm all items before requesting review.
130+
-->
131+
- [ ] I have self-reviewed my code
132+
- [ ] Code follows project standards and conventions
133+
- [ ] Tests have been added or updated
134+
- [ ] Documentation has been updated (if applicable)
135+
- [ ] No new warnings or lint errors
136+
- [ ] Changes are backward compatible or breaking changes are documented
137+
138+
---
139+
140+
## 📚 Additional Context
141+
<!--
142+
Any extra information that may help reviewers understand this PR.
143+
Links, references, or follow-up work.
144+
-->

0 commit comments

Comments
 (0)