Skip to content

Update README with VS Code Marketplace link and installation notes #24

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.

Sign up for GitHub

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
hoangsonww merged 2 commits into from
Apr 29, 2026
+18 −0
Merged

Update README with VS Code Marketplace link and installation notes #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0e4b32f
docs: add VS Code Marketplace link and Forge runtime installation not…
hoangsonww Apr 27, 2026
6d14dca
ci: force shell: bash on release install steps so the Windows runner …
hoangsonww Apr 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,10 @@ jobs:
cache: npm
- name: Install dependencies
# npm/cli#4828 self-heal (see ci.yml for rationale).
# `shell: bash` so the Windows runner uses Git Bash instead of
# PowerShell — `2>/dev/null`, `||`-grouped fallbacks, and `rm -rf`
# are bash-only and PowerShell mis-parses `/dev/null` as a path.
shell: bash
run: |
npm ci --ignore-scripts || {
echo "::warning::npm ci failed — falling back to npm install (npm/cli#4828)"
Expand Down Expand Up @@ -87,6 +91,10 @@ jobs:
cache: npm
- name: Install dependencies
# npm/cli#4828 self-heal (see ci.yml for rationale).
# `shell: bash` so the Windows runner uses Git Bash instead of
# PowerShell — `2>/dev/null`, `||`-grouped fallbacks, and `rm -rf`
# are bash-only and PowerShell mis-parses `/dev/null` as a path.
shell: bash
run: |
npm ci --ignore-scripts || {
echo "::warning::npm ci failed — falling back to npm install (npm/cli#4828)"
Expand Down Expand Up @@ -220,6 +228,10 @@ jobs:
cache: npm
- name: Install dependencies
# npm/cli#4828 self-heal (see ci.yml for rationale).
# `shell: bash` so the Windows runner uses Git Bash instead of
# PowerShell — `2>/dev/null`, `||`-grouped fallbacks, and `rm -rf`
# are bash-only and PowerShell mis-parses `/dev/null` as a path.
shell: bash
run: |
npm ci --ignore-scripts || {
echo "::warning::npm ci failed — falling back to npm install (npm/cli#4828)"
Expand Down
6 changes: 6 additions & 0 deletions vscode-extension/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,12 @@ The full Forge agentic coding workflow, brought into your editor. Run tasks from
- **Click-through to task detail**: every recent task in the sidebar opens directly into its conversation, plan, and result, not just the dashboard home.
- **Workspace-aware**: respects your VS Code workspace folder by default and lets you override the working directory per project, or pick a fresh one with a folder picker.

> [!TIP]
> Marketplace Link: [https://marketplace.visualstudio.com/items?itemName=hoangsonw.forge-agentic-coding-cli](https://marketplace.visualstudio.com/items?itemName=hoangsonw.forge-agentic-coding-cli).

> [!IMPORTANT]
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Apr 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The extension's source code (specifically in extension.ts) contains a link to the documentation with an anchor #installation. However, the README currently lacks an Installation header, which means the link will not navigate to the correct section when clicked from the extension's warning message. Adding an ## Installation header here will fix this and provide a clear section for the installation notes.

Suggested change
> [!IMPORTANT]
## Installation
> [!IMPORTANT]

> Be sure to install the Forge runtime (`@hoangsonw/forge`) globally before using the extension, as it relies on Forge for all interactions. The extension does not bundle the runtime, so it can stay up to date independently.

## Quick start

```bash
Expand Down
Loading