-
Notifications
You must be signed in to change notification settings - Fork 489
refactor: use environment variables for git configuration in test rep… #336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
1d7b64c
refactor: use environment variables for git configuration in test rep…
eae60ab
feat: update README logo to SVG format
9838144
feat: add GitHub issue fix command and release command
6d4ab9c
feat: implement version-based migrations for global settings
abe272e
fix: remove TypeScript type annotations from bumpVersion function
f32f3e8
feat: enhance port management and server initialization process
75143c0
refactor: clean up whitespace and improve prompt formatting in port m…
b867ca1
refactor: update window close behavior for macOS and other platforms
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,74 @@ | ||
| # GitHub Issue Fix Command | ||
|
|
||
| Fetch a GitHub issue by number, verify it's a real issue, and fix it if valid. | ||
|
|
||
| ## Usage | ||
|
|
||
| This command accepts a GitHub issue number as input (e.g., `123`). | ||
|
|
||
| ## Instructions | ||
|
|
||
| 1. **Get the issue number from the user** | ||
| - The issue number should be provided as an argument to this command | ||
| - If no number is provided, ask the user for it | ||
|
|
||
| 2. **Fetch the GitHub issue** | ||
| - Determine the current project path (check if there's a current project context) | ||
| - Verify the project has a GitHub remote: | ||
| ```bash | ||
| git remote get-url origin | ||
| ``` | ||
| - Fetch the issue details using GitHub CLI: | ||
| ```bash | ||
| gh issue view <ISSUE_NUMBER> --json number,title,state,author,createdAt,labels,url,body,assignees | ||
| ``` | ||
| - If the command fails, report the error and stop | ||
|
|
||
| 3. **Verify the issue is real and valid** | ||
| - Check that the issue exists (not 404) | ||
| - Check the issue state: | ||
| - If **closed**: Inform the user and ask if they still want to proceed | ||
| - If **open**: Proceed with validation | ||
| - Review the issue content: | ||
| - Read the title and body to understand what needs to be fixed | ||
| - Check labels for context (bug, enhancement, etc.) | ||
| - Note any assignees or linked PRs | ||
|
|
||
| 4. **Validate the issue** | ||
| - Determine if this is a legitimate issue that needs fixing: | ||
| - Is the description clear and actionable? | ||
| - Does it describe a real problem or feature request? | ||
| - Are there any obvious signs it's spam or invalid? | ||
| - If the issue seems invalid or unclear: | ||
| - Report findings to the user | ||
| - Ask if they want to proceed anyway | ||
| - Stop if user confirms it's not valid | ||
|
|
||
| 5. **If the issue is valid, proceed to fix it** | ||
| - Analyze what needs to be done based on the issue description | ||
| - Check the current codebase state: | ||
| - Run relevant tests to see current behavior | ||
| - Check if the issue is already fixed | ||
| - Look for related code that might need changes | ||
| - Implement the fix: | ||
| - Make necessary code changes | ||
| - Update or add tests as needed | ||
| - Ensure the fix addresses the issue description | ||
| - Verify the fix: | ||
| - Run tests to ensure nothing broke | ||
| - If possible, manually verify the fix addresses the issue | ||
|
|
||
| 6. **Report summary** | ||
| - Issue number and title | ||
| - Issue state (open/closed) | ||
| - Whether the issue was validated as real | ||
| - What was fixed (if anything) | ||
| - Any tests that were updated or added | ||
| - Next steps (if any) | ||
|
|
||
| ## Error Handling | ||
|
|
||
| - If GitHub CLI (`gh`) is not installed or authenticated, report error and stop | ||
| - If the project doesn't have a GitHub remote, report error and stop | ||
| - If the issue number doesn't exist, report error and stop | ||
| - If the issue is unclear or invalid, report findings and ask user before proceeding |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,56 @@ | ||
| # Release Command | ||
|
|
||
| Bump the package.json version (major, minor, or patch) and build the Electron app with the new version. | ||
|
|
||
| ## Usage | ||
|
|
||
| This command accepts a version bump type as input: | ||
|
|
||
| - `patch` - Bump patch version (0.1.0 -> 0.1.1) | ||
| - `minor` - Bump minor version (0.1.0 -> 0.2.0) | ||
| - `major` - Bump major version (0.1.0 -> 1.0.0) | ||
|
|
||
| ## Instructions | ||
|
|
||
| 1. **Get the bump type from the user** | ||
| - The bump type should be provided as an argument (patch, minor, or major) | ||
| - If no type is provided, ask the user which type they want | ||
|
|
||
| 2. **Bump the version** | ||
| - Run the version bump script: | ||
| ```bash | ||
| node apps/ui/scripts/bump-version.mjs <type> | ||
| ``` | ||
| - This updates both `apps/ui/package.json` and `apps/server/package.json` with the new version (keeps them in sync) | ||
| - Verify the version was updated correctly by checking the output | ||
|
|
||
| 3. **Build the Electron app** | ||
| - Run the electron build: | ||
| ```bash | ||
| npm run build:electron --workspace=apps/ui | ||
| ``` | ||
| - The build process automatically: | ||
| - Uses the version from `package.json` for artifact names (e.g., `Automaker-1.2.3-x64.zip`) | ||
| - Injects the version into the app via Vite's `__APP_VERSION__` constant | ||
| - Displays the version below the logo in the sidebar | ||
|
|
||
| 4. **Verify the release** | ||
| - Check that the build completed successfully | ||
| - Confirm the version appears correctly in the built artifacts | ||
| - The version will be displayed in the app UI below the logo | ||
|
|
||
| ## Version Centralization | ||
|
|
||
| The version is centralized and synchronized in both `apps/ui/package.json` and `apps/server/package.json`: | ||
|
|
||
| - **Electron builds**: Automatically read from `apps/ui/package.json` via electron-builder's `${version}` variable in `artifactName` | ||
| - **App display**: Injected at build time via Vite's `define` config as `__APP_VERSION__` constant (defined in `apps/ui/vite.config.mts`) | ||
| - **Server API**: Read from `apps/server/package.json` via `apps/server/src/lib/version.ts` utility (used in health check endpoints) | ||
| - **Type safety**: Defined in `apps/ui/src/vite-env.d.ts` as `declare const __APP_VERSION__: string` | ||
|
|
||
| This ensures consistency across: | ||
|
|
||
| - Build artifact names (e.g., `Automaker-1.2.3-x64.zip`) | ||
| - App UI display (shown as `v1.2.3` below the logo in `apps/ui/src/components/layout/sidebar/components/automaker-logo.tsx`) | ||
| - Server health endpoints (`/` and `/detailed`) | ||
| - Package metadata (both UI and server packages stay in sync) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,117 @@ | ||
| name: Bug Report | ||
| description: File a bug report to help us improve Automaker | ||
| title: '[Bug]: ' | ||
| labels: ['bug'] | ||
| body: | ||
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| Thanks for taking the time to report a bug! Please fill out the form below with as much detail as possible. | ||
|
|
||
| - type: dropdown | ||
| id: operating-system | ||
| attributes: | ||
| label: Operating System | ||
| description: What operating system are you using? | ||
| options: | ||
| - macOS | ||
| - Windows | ||
| - Linux | ||
| - Other | ||
| default: 0 | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: dropdown | ||
| id: run-mode | ||
| attributes: | ||
| label: Run Mode | ||
| description: How are you running Automaker? | ||
| options: | ||
| - Electron (Desktop App) | ||
| - Web (Browser) | ||
| - Docker | ||
| default: 0 | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: input | ||
| id: app-version | ||
| attributes: | ||
| label: App Version | ||
| description: What version of Automaker are you using? (e.g., 0.1.0) | ||
| placeholder: '0.1.0' | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: textarea | ||
| id: bug-description | ||
| attributes: | ||
| label: Bug Description | ||
| description: A clear and concise description of what the bug is. | ||
| placeholder: Describe the bug... | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: textarea | ||
| id: steps-to-reproduce | ||
| attributes: | ||
| label: Steps to Reproduce | ||
| description: Steps to reproduce the behavior | ||
| placeholder: | | ||
| 1. Go to '...' | ||
| 2. Click on '...' | ||
| 3. Scroll down to '...' | ||
| 4. See error | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: textarea | ||
| id: expected-behavior | ||
| attributes: | ||
| label: Expected Behavior | ||
| description: A clear and concise description of what you expected to happen. | ||
| placeholder: What should have happened? | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: textarea | ||
| id: actual-behavior | ||
| attributes: | ||
| label: Actual Behavior | ||
| description: A clear and concise description of what actually happened. | ||
| placeholder: What actually happened? | ||
| validations: | ||
| required: true | ||
|
|
||
| - type: textarea | ||
| id: screenshots | ||
| attributes: | ||
| label: Screenshots | ||
| description: If applicable, add screenshots to help explain your problem. | ||
| placeholder: Drag and drop screenshots here or paste image URLs | ||
|
|
||
| - type: textarea | ||
| id: logs | ||
| attributes: | ||
| label: Relevant Logs | ||
| description: If applicable, paste relevant logs or error messages. | ||
| placeholder: Paste logs here... | ||
| render: shell | ||
|
|
||
| - type: textarea | ||
| id: additional-context | ||
| attributes: | ||
| label: Additional Context | ||
| description: Add any other context about the problem here. | ||
| placeholder: Any additional information that might be helpful... | ||
|
|
||
| - type: checkboxes | ||
| id: terms | ||
| attributes: | ||
| label: Checklist | ||
| options: | ||
| - label: I have searched existing issues to ensure this bug hasn't been reported already | ||
| required: true | ||
| - label: I have provided all required information above | ||
| required: true |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| /** | ||
| * Version utility - Reads version from package.json | ||
| */ | ||
|
|
||
| import { readFileSync } from 'fs'; | ||
| import { fileURLToPath } from 'url'; | ||
| import { dirname, join } from 'path'; | ||
|
|
||
| const __filename = fileURLToPath(import.meta.url); | ||
| const __dirname = dirname(__filename); | ||
|
|
||
| let cachedVersion: string | null = null; | ||
|
|
||
| /** | ||
| * Get the version from package.json | ||
| * Caches the result for performance | ||
| */ | ||
| export function getVersion(): string { | ||
| if (cachedVersion) { | ||
| return cachedVersion; | ||
| } | ||
|
|
||
| try { | ||
| const packageJsonPath = join(__dirname, '..', '..', 'package.json'); | ||
| const packageJson = JSON.parse(readFileSync(packageJsonPath, 'utf-8')); | ||
| const version = packageJson.version || '0.0.0'; | ||
| cachedVersion = version; | ||
| return version; | ||
| } catch (error) { | ||
| console.warn('Failed to read version from package.json:', error); | ||
| return '0.0.0'; | ||
| } | ||
| } |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
@anthropic-ai/claude-agent-sdk 0.1.73 0.1.74 0.1.75 0.1.76 changelog release notes breaking changes💡 Result:
I found package/version metadata and pointers to the SDK changelog; specific release notes for 0.1.73 → 0.1.76 are published in the repository CHANGELOG and in the package registry:
Links:
If you want, I can fetch the CHANGELOG.md from the TypeScript repo and extract the full release notes and any breaking changes for 0.1.73–0.1.76. Which would you prefer?
🌐 Web query:
anthropic-ai/typescript-sdk claude-agent-sdk GitHub repository CHANGELOG💡 Result:
I found the repository and its CHANGELOG.md:
References:
[1] https://github.com/anthropics/claude-agent-sdk-typescript
[2] https://docs.claude.com/en/docs/agent-sdk/overview
🏁 Script executed:
curl -s https://raw.githubusercontent.com/anthropics/claude-agent-sdk-typescript/main/CHANGELOG.md | head -200Repository: AutoMaker-Org/automaker
Length of output: 5342
🏁 Script executed:
Repository: AutoMaker-Org/automaker
Length of output: 49
🏁 Script executed:
Repository: AutoMaker-Org/automaker
Length of output: 187
🏁 Script executed:
Repository: AutoMaker-Org/automaker
Length of output: 49
🏁 Script executed:
Repository: AutoMaker-Org/automaker
Length of output: 345
🏁 Script executed:
Repository: AutoMaker-Org/automaker
Length of output: 150
🏁 Script executed:
Repository: AutoMaker-Org/automaker
Length of output: 223
Version 0.1.76 does not appear to be a published release.
The specified version
0.1.76has no published timestamp in npm and no corresponding GitHub release. The latest published version is0.1.74(Dec 19, 2025). Versions 0.1.75 and 0.1.76 exist in npm metadata but showtime: null, indicating they are not properly released.The recent documented versions (0.1.73–0.1.74) contain only bug fixes with no breaking changes. Verify whether the version in package.json should be
0.1.74instead, or confirm that 0.1.76 is the intended version despite not being published yet.🤖 Prompt for AI Agents