Skip to content

[Repo Assist] release: consolidate critical bug fixes for v0.0.10 #98

@github-actions

Description

@github-actions

🤖 This PR was created by Repo Assist, an automated AI assistant.

This is a release candidate for v0.0.10 that consolidates all critical bug fixes from the many open Repo Assist PRs into a single, reviewable change. Merging this one PR gives you a releasable 0.0.10.

For the maintainer: Rather than reviewing 35 individual PRs, you can review this single PR. It incorporates the most important fixes. The other Repo Assist PRs can be closed after this merges.


Changes

Bug Fixes

Compatibility

Polish

  • Only reload settings on phpcbf.* config changes — prevents unnecessary loadSettings() calls on every VS Code settings change (e.g. editor font size).
  • Version bump to 0.0.10 in package.json and CHANGELOG.md.

Closes

Closes #7, #16, #19, #27, #35, #36, #38, #39


Test Status

Unit tests pass: node --test test/unit.test.js — 7/7 tests pass
Syntax check: node --check extension.js — no syntax errors
⚠️ Integration tests: VS Code integration tests require a GUI environment and cannot run in CI. The logic changes are unit-testable; the formatting provider changes follow the VS Code extension API contract.


Relationship to Other Open PRs

This PR supersedes the following Repo Assist PRs, which can be closed after merging:

Human PR #97 (PHP_CodeSniffer link update by @rodrigoprimo) should be merged separately — it is not included here.

Generated by Repo Assist ·

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@346204513ecfa08b81566450d7d599556807389f

Warning

🛡️ Protected Files

This was originally intended as a pull request, but the patch modifies protected files: package.json.

These files may affect project dependencies, CI/CD pipelines, or agent behaviour. Please review the changes carefully before creating the pull request.

Click here to create the pull request once you have reviewed the changes

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions