add tool to synchronize add-on repository with latest addonTemplate by abdel792 · Pull Request #46 · nvaccess/AddonTemplate

abdel792 · 2026-08-04T10:53:28Z

Link to issue number:

Replaces #41.

Summary of the issue:

While upgrading an existing add-on using standard Git commands remains fully supported, some add-on developers prefer an automated and dedicated tool to streamline the process. Manual step-by-step migration of metadata (from buildVars.py to pyproject.toml) and file merges can require extra care and verification. Providing an automated script offers a convenient alternative for developers who wish to perform these updates quickly and with built-in AST-based metadata handling.

Description of developer facing changes:

Introduces syncAddonWithTemplate.py at the repository root as an automated alternative to Git-based manual upgrades for add-on developers.
Protects template-specific files, including .github/workflows/unitTests.yml and tests/, ensuring they are excluded from add-on synchronization.
Excludes both syncAddonWithTemplate.py and the tests/ directory from static analysis in pyproject.toml (ruff and pyright).
Adds a dedicated unit test suite for the synchronization logic (tests/unit/test_syncAddonWithTemplate.py).
Updates documentation for updating existing add-ons and executing unit tests.

Description of development approach:

Synchronization Engine Creation: Implemented syncAddonWithTemplate.py using an AST-aware approach to seamlessly migrate legacy buildVars.py metadata or modern AddonInfo setups into pyproject.toml. It supports timestamped backups, custom exclusions via .addonmergeignore, and includes .github/workflows/unitTests.yml in PROTECTED_ELEMENTS.
Linter Exclusion Rules: Configured pyproject.toml to exclude syncAddonWithTemplate.py and tests/ from ruff and pyright checks.
Verification Suite & Execution Order: Created a dedicated unit test suite (tests/unit/test_syncAddonWithTemplate.py) using unittest and tempfile, utilizing a load_tests hook to guarantee deterministic test execution order.
Documentation Integration: Updated technical guides to detail CLI usage, available options, and unit testing commands.

Testing strategy:

Validated the synchronization script and unit test suite locally using uv:

Executed syncAddonWithTemplate.py across various CLI modes:
- Standard Mode (inside add-on repo, -ad is optional):

uv run python syncAddonWithTemplate.py

External Directory Mode:

uv run python /path/to/syncAddonWithTemplate.py -ad /path/to/my-nvda-addon

Dry Run Simulation:

uv run python syncAddonWithTemplate.py --dry-run

Verified that backup folders (<addon>_bak_<timestamp>) were generated, .addonmergeignore rules were respected, and protected elements (including .github/workflows/unitTests.yml and tests/) were not pushed to target add-on repositories.
Executed the unit test suite via unittest:

uv run python -m unittest -v tests/unit/test_syncAddonWithTemplate.py

Confirmed all tests passed successfully.
4. Confirmed ruff and pyright ignore syncAddonWithTemplate.py and tests/.

Known issues with pull request:

None.

Code Review Checklist

Testing: Tested manually across diverse execution paths and validated via local unit tests. Steps to reproduce are detailed in the testing strategy.
Compatibility: Developer-facing infrastructure tool; introduces no breaking changes to existing repository behaviors.
Documentation: Technical developer documentation has been explicitly updated.
UX of all users considered: Not applicable (Developer-facing infrastructure tool only).
Security precautions taken: Not applicable (Runs locally in isolated temporary directories during development).

Introduces the syncAddonWithTemplate.py automation tool to streamline synchronizing add-on metadata and infrastructure with upstream template updates. Detailed changes: - Added `syncAddonWithTemplate.py` at repository root to handle AST-aware merging of buildVars.py and pyproject.toml configuration. - Configured `PROTECTED_ELEMENTS` in the sync script to prevent overwriting template-specific files (e.g., `.github/workflows/unitTests.yml` and `tests/`). - Added `.addonmergeignore` support for defining project-specific file exclusion rules during synchronization. - Added dependencies for the sync tool to `pyproject.toml`. - Added `tests/unit/test_syncAddonWithTemplate.py` to validate metadata parsing, AST transformations, TOML formatting, and execution ordering. - Updated `pyproject.toml` to exclude `syncAddonWithTemplate.py` alongside the `tests/` directory from ruff and pyright checks. - Updated `docs/managementFromGit/updatingExistingAddons.md` with full usage instructions, CLI flags, and execution modes for the sync script. - Updated `docs/unitTesting.md` with guidelines for running unit tests locally using unittest and uv.

Update testFormatAuthorList in test_syncAddonWithTemplate.py to assert that empty author email keys are omitted rather than expecting an empty string, matching syncAddonWithTemplate.py behavior.

…umentation Update description of testFormatAuthorList to document that empty email fields are omitted for PEP 621 compliance.

Copilot

Pull request overview

Adds a developer-facing synchronization tool to help NVDA add-on authors update their repositories to the latest AddonTemplate structure, including AST-aware metadata handling and TOML merging, with accompanying unit tests and documentation updates.

Changes:

Introduces syncAddonWithTemplate.py to sync template infrastructure while merging buildVars.py and pyproject.toml.
Adds unit tests for key merge/formatting behavior and a small template sanity suite.
Updates dependency groups/docs to support running the sync tool and the unit test suite.

Reviewed changes

Copilot reviewed 8 out of 10 changed files in this pull request and generated 8 comments.

Show a summary per file

File	Description
`syncAddonWithTemplate.py`	New sync/merge engine (AST + tomlkit) for updating add-on repos from the template.
`tests/unit/test_syncAddonWithTemplate.py`	Unit tests for metadata extraction, buildVars merge, TOML indentation, and dependency merging.
`tests/unit/template/sanity.py`	Minimal sanity tests intended to validate CI test discovery/execution.
`docs/managementFromGit/updatingExistingAddons.md`	Expanded guidance for updating add-ons (automated tool + manual merge).
`docs/unitTesting.md`	Updated instructions for running the unit tests and describing the new suites.
`pyproject.toml`	Adds `tomlkit`, updates `pyright`, and excludes the new sync script/tests from ruff/pyright.
`uv.lock`	Locks `tomlkit` and bumps `pyright` to match `pyproject.toml`.
`tests/__init__.py`	Updates package docstring.
`tests/unit/__init__.py`	Updates package docstring.
`.addonmergeignore`	Present at repo root (empty in this PR context).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

…ty test - Move test infrastructure docstring from root unit tests to template submodule. - Revert root `tests/__init__.py` docstring to reflect all test types (system and unit). - Remove obsolete `sanity.py` test file.

abdel792 · 2026-08-05T19:41:30Z

Hi @seanbudd,
Thanks for your feedback! I have updated the branch accordingly:

Docstrings adjustment: I moved the test infrastructure docstring from root unit tests to the template submodule and restored the root tests/__init__.py docstring to reflect all test types (system and unit).
Sanity test removal: I removed the obsolete sanity.py test file.

- Replace underscores with hyphens in `getBasePackageName` and `legacyToolingBases` to handle equivalent Python package name formats during dependency merges. - Bootstrap `.addonmergeignore` from template on first sync if absent locally, allowing it to self-reference and manage its own persistence dynamically.

abdel792 · 2026-08-05T20:00:50Z

@Copilot,
Here are the updates I made regarding your remarks on normalization and .addonmergeignore:

Package Name Normalization: I replaced underscores with hyphens in getBasePackageName and legacyToolingBases to consistently handle equivalent Python package name formats during dependency merges.
Dynamic Bootstrapping & Self-Exclusion: Instead of adding .addonmergeignore to protectedElements, I updated syncAddonWithTemplate.setupAddonMergeIgnore to bootstrap .addonmergeignore from the template on the first sync if it is absent locally, ensuring it includes its own self-exclusion. I prefer this approach as it allows the file to self-reference and manage its own persistence dynamically.

- Replace `methodOrder.index()` with `orderIndex.get(a, defaultOrder)` map. - Prevent `ValueError` when running tests on inherited or dynamic methods.

abdel792 · 2026-08-05T20:10:33Z

@Copilot,
Regarding your comment on the load_tests implementation in test_syncAddonWithTemplate.py:

Robust Test Sorting: I updated load_tests to use an orderIndex lookup dictionary with orderIndex.get(a, defaultOrder) instead of methodOrder.index().
Error Prevention: I added this to prevent potential ValueError exceptions if inherited or dynamic test methods are present during test execution.

- Fix incorrect path for `test_syncAddonWithTemplate.py` in `unitTesting.md`. - Clarify `tomlkit` installation requirement and fix no-argument command example in `updatingExistingAddons.md`.

abdel792 · 2026-08-05T20:19:17Z

@Copilot,
Regarding your feedback on the documentation:

Unit Test Path Fix: I fixed the incorrect path for test_syncAddonWithTemplate.py in docs/unitTesting.md.
CLI Usage & Dependency Clarification: I clarified the tomlkit installation requirement and corrected the no-argument command example in docs/managementFromGit/updatingExistingAddons.md.

- Add testSetupAddonMergeIgnore and testAddonMergeIgnore to test_syncAddonWithTemplate.py - Document both new tests in docs/unitTesting.md

abdel792 · 2026-08-05T20:38:34Z

Hi @seanbudd, @Copilot,

Regarding the test coverage for .addonmergeignore:

Unit Tests: I added testSetupAddonMergeIgnore and testAddonMergeIgnore to test_syncAddonWithTemplate.py to verify both the creation/bootstrapping behavior when missing and the actual file exclusion during synchronization.
Documentation: I documented both new test methods in docs/unitTesting.md.

seanbudd · 2026-08-06T01:35:09Z

 	"ruff==0.14.5",
 	"prek==0.4.8",
-	"pyright[nodejs]==1.1.407",
+	"pyright[nodejs]==1.1.411",


do we need to update pyright in this PR?

…mplate.py

abdel792 · 2026-08-06T20:49:41Z

Hi @seanbudd,

When running pyright on version 1.1.407 via uv (e.g., uv run pyright addon), the underlying Python wrapper package (pyright-python) checks for upstream NPM release updates and systematically outputs a warning to stderr before executing the type checker:

WARNING: there is a new pyright version available (v1.1.407 -> v1.1.411).
Please install the new version or set PYRIGHT_PYTHON_FORCE_VERSION to `latest`

I bumped the lock version to 1.1.411 in pyproject.toml to eliminate this noise during local check runs and developer workflows.

Let me know if you would still prefer me to revert it to keep the PR scope strictly minimal!

- Fix casing for AddonTemplate repository URL in updatingExistingAddons.md - Remove detailed syncAddonWithTemplate test suite breakdown in unitTesting.md to keep coverage in docstrings

abdel792 · 2026-08-06T21:12:17Z

Thanks for the review and all these helpful suggestions, @seanbudd!

I have addressed the quick fixes and documentation updates:

Restored the exact casing for AddonTemplate in docs/managementFromGit/updatingExistingAddons.md.
Removed the detailed test suite section from docs/unitTesting.md (relying on test docstrings instead).
Fixed the missing newline at the end of test_syncAddonWithTemplate.py.

Regarding your suggestion to split syncAddonWithTemplate.py into submodules: I completely agree, it's a great idea that will make the code much cleaner and easier to maintain!

I'm currently refactoring the code into submodules, writing the requested additional test cases, and running all necessary tests. I will address all of your remaining feedback and suggestions throughout this process and post a full update over the weekend.

I'll leave the PR in draft mode until everything is ready for review.

abdel792 · 2026-08-06T22:19:09Z

Sean, regarding your comment on legacyToolingBases:

I'm currently implementing a solution for this and will push it in my next commit over the weekend, as I need to finish up some work commitments first.

The previous legacyToolingBases set was indeed handling this, but as you pointed out, maintaining such a hardcoded list long-term is cumbersome.

Replacing it with a dynamic lookup alongside a minimal mapping dictionary for non-supported/replaced dependencies (like pre-commit) makes maintenance much simpler.

The updated logic now dynamically collects all tooling packages directly from the template's dependencies and dependency-groups in pyproject.toml.

Additionally, for deprecated tools that were replaced in the template (such as pre-commit being replaced by prek), I introduced a lightweight dictionary (REPLACED_PACKAGES = {"pre-commit": "prek"}).

This maps replaced tools to their modern template equivalents so they aren't accidentally preserved as custom dependencies.

Here is a snippet of how the dynamic collection works:

# Dynamically collect all template packages (dependencies + dependency-groups)
templateBases: set[str] = {
	getBasePackageName(d) for d in tplDeps if isinstance(d, str)
}
if "dependency-groups" in mergedData and isinstance(mergedData["dependency-groups"], MutableMapping):
	for grp in mergedData["dependency-groups"].values():
		if isinstance(grp, (list, MutableSequence)):
			for grpItem in grp:
				if isinstance(grpItem, str):
					templateBases.add(getBasePackageName(grpItem))

- Add syncAddonTool package directory to lighten syncAddonWithTemplate.py. - Import submodules from syncAddonTool into syncAddonWithTemplate.py for improved code readability and structure. - Add test fixtures directory to decouple legacy dictionaries and sample files from test_syncAddonWithTemplate.py. - Add unit tests verifying version priority handling between user dependencies and template dependencies. - Add syncAddonTool.spec at repository root to streamline executable generation with PyInstaller.

…tandalone executable - Update docs/managementFromGit/updatingExistingAddon.md to document the syncAddonTool directory. - Add instructions for building and running the standalone executable using PyInstaller and `uv run --with pyinstaller`.

abdel792 · 2026-08-09T21:53:14Z

In the last two commits, I made the following updates:

First commit: Added the build/ and dist/ directories to .gitignore to prevent tracking PyInstaller build artifacts.
Second commit: Fixed an issue causing extra consecutive empty lines to be added to TOML files after generation.

abdel792 · 2026-08-10T22:56:04Z

Hi Sean,

Thanks for the feedback! I've noted all your points and will work on applying these updates tomorrow or the day after.

- Move `syncAddonTool.spec` into the `syncAddonTool/` package directory. - Rename unit test module from `test_syncAddonWithTemplate.py` to `test_syncAddonTool.py` in `tests/unit/template/`. - Update `pyproject.toml` to remove redundant Pyright and Ruff exclusions for the old script and spec file (the spec file is now covered by the existing `syncAddonTool` directory rule). - Update `docs/unittesting.md` to reference `test_syncAddonTool.py`.

abdel792 · 2026-08-11T06:53:04Z

Hi Sean,

I have updated the PR with the following cleanup and refactoring changes:

Removed deprecated script: Deleted syncAddonWithTemplate.py and moved syncAddonTool.spec inside the syncAddonTool/ directory.
Renamed unit test: Renamed test_syncAddonWithTemplate.py to test_syncAddonTool.py under tests/unit/template/.
Updated linter configuration: Removed obsolete exclusions in pyproject.toml for Pyright and Ruff, as syncAddonTool.spec is now naturally handled by the existing syncAddonTool directory inclusion/exclusion rules.
Documentation fix: Updated docs/unittesting.md to reflect the new test file name (test_syncAddonTool.py).

the syncAddonTool workflow for syncing add-ons with AddonTemplate.

abdel792 · 2026-08-11T15:32:26Z

Hi Sean,

I have updated docs/managementFromGit/updatingExistingAddons.md to document the syncAddonTool automated synchronization process.

While working on these changes, I also noticed three minor pre-existing typos/formatting issues in the master version of this file:

"submolder" instead of "subfolder" in item 3 under Pre-requisites.
Unmatched quote / trailing dash in backtick: if you haven't passed the "--squash- flag, under Before you begin.
Duplicate section: ## Adding the template repository appears both in the top pre-requisites section and under the manual update section.

I deliberately left these untouched to keep the diff strictly focused on introducing syncAddonTool.

However, if you'd like me to clean those up in this PR as well, I'd be glad to push a quick fix!

Remove instances of `python -m syncAddonTool.py` from updatingExistingAddons.md to keep only valid module and directory execution syntaxes.

abdel792 · 2026-08-11T17:51:05Z

Hi Sean,

Just pushed a quick update to docs/managementFromGit/updatingExistingAddons.md to fix the execution syntax in the examples (removing the .py extension when using -m).

As mentioned earlier, I haven't touched the three pre-existing typos/formatting issues yet—let me know if you'd like me to fix them in this PR or leave them for later.

- Add missing -v/--verbose flag to CLI options table in docs/managementFromGit/updatingExistingAddons.md. - Suppress redundant dependency decision logs when running with --verbose.

abdel792 · 2026-08-12T06:00:46Z

Hi Sean,

Just pushed a new update to docs/managementFromGit/updatingExistingAddons.md to add the -v / --verbose flag to the options table and clean up the debug output during dependency merging. Running syncAddonTool commands with -v now gives much cleaner, deterministic logs without duplicate decision entries.

As agreed, I haven't touched the three minor pre-existing typos/formatting issues.

Prepend full TOML key path (e.g. tool.ruff.include) when logging list merges in pyproject.toml to eliminate ambiguity.

abdel792 · 2026-08-12T19:36:54Z

While reviewing a verbose debug report, I noticed that section key logging during the pyproject.toml merge was ambiguous for duplicate keys like include and exclude (it wasn't clear whether they belonged to Ruff, Pyright, or another section).

I just pushed a small refinement to pass the full TOML context path to the merge logger.

This makes the debug output much more explicit and easier to trace:

Before: [DEBUG] Merging list [include]
Now: [DEBUG] Merging list [tool.ruff.include] / [DEBUG] Merging list [tool.pyright.include]

abdel792 · 2026-08-13T07:14:25Z

Hi @seanbudd,

I just merged master into this PR branch to ensure it remains fast-forwardable on top of master.

Copilot

🔵 Needs a closer look

It adds a large new tool that destructively rewrites/merges files in developer repositories with intricate AST/TOML logic and untested CLI/backup/git paths, alongside documentation that overstates supported behavior, so human review is warranted.

Review details

Files reviewed: 21/23 changed files
Comments generated: 7
Review effort level: Balanced

+- Inside this file, list the names, relative paths, or glob patterns of the files or folders you want the tool to skip during synchronization.
+- The file uses standard `.gitignore` pattern matching syntax (parsed via `pathspec`).


+
+* **Add-on Synchronization Tool Tests:**
+  ``` bash
+  uv run python -m unittest -v tests/unit/template/test_syncAddonTool


 You can merge the latest template changes into your repository instead of manually copying updated files.

-This document explains the recommended update procedure.
+*This document explains the update procedures, including both the recommended automated method using `syncAddonTool` and the manual Git merge workflow."*


+  uv run python syncAddonTool -ad /path/to/my-nvda-addon -td /path/to/local/AddonTemplate
+  ```
+
+- **Syntax D (Standalone executable)**:


 ## Running Tests Locally

-To run the unit test suite locally using `uv`:
+For unit tests to execute successfully, target modules (such as `syncAddonWithTemplate.py`) must be located at the root of the repository as sibling files to the `tests/` directory (at the same hierarchical level). This ensures Python's module discovery properly imports scripts when `unittest` runs from the project root.


 	"__pycache__",
 	".venv",
 	"buildVars.py",
+	"syncAddonTool",


+		"tomlkit",
+		"pathspec",


seanbudd · 2026-09-04T07:40:34Z

@nvdaes could we have your assistance in reviewing this please?

seanbudd · 2026-09-04T09:32:15Z

 	"ruff==0.14.5",
 	"prek==0.4.8",
-	"pyright[nodejs]==1.1.407",
+	"pyright[nodejs]==1.1.411",


I don't know why https://github.com/nvaccess/AddonTemplate/pull/46/changes#r3725285433 was marked as resolved. I have unmarked it. Please update pyright in a separate PR

seanbudd · 2026-09-04T09:33:11Z

+##### Crucial Requirements & Design Constraints
+
+1. **Automatic Self-Exclusion:**
+   The update tool automatically protects `.addonmergeignore` itself from being overwritten during synchronization. Even if `.addonmergeignore` is present in the template repository, the target add-on's local `.addonmergeignore` file is preserved without needing to explicitly list itself.


please put new sentences on new lines in markdown files for diffing and readability

nvdaes · 2026-09-04T16:57:39Z

@seanbudd wrote:

@nvdaes could we have your assistance in reviewing this please?

Yes, but what would you like? Should I review changes providing feedback, or are you asking me to address your review?
Abdel is not available at this moment. He will be able to make changes after some weeks.

abdel792 added 3 commits August 4, 2026 12:12

test(sync): update testFormatAuthorList for PEP 621 compliance

3553ac3

Update testFormatAuthorList in test_syncAddonWithTemplate.py to assert that empty author email keys are omitted rather than expecting an empty string, matching syncAddonWithTemplate.py behavior.

docs(unitTesting): clarify testFormatAuthorList email omission in doc…

bc4816d

…umentation Update description of testFormatAuthorList to document that empty email fields are omitted for PEP 621 compliance.

seanbudd reviewed Aug 5, 2026

View reviewed changes

Comment thread tests/unit/template/test_syncAddonTool.py

Comment thread tests/unit/template/sanity.py Outdated

Comment thread tests/unit/__init__.py Outdated

Comment thread tests/__init__.py Outdated

seanbudd requested a lite review from Copilot August 5, 2026 05:43

seanbudd marked this pull request as draft August 5, 2026 05:43

Copilot started reviewing on behalf of seanbudd August 5, 2026 05:43 View session

Copilot AI reviewed Aug 5, 2026

View reviewed changes

test(sync): make load_tests sorting robust against inherited methods

f64404c

- Replace `methodOrder.index()` with `orderIndex.get(a, defaultOrder)` map. - Prevent `ValueError` when running tests on inherited or dynamic methods.

docs(sync): fix unit test path and CLI usage examples

a8ef694

- Fix incorrect path for `test_syncAddonWithTemplate.py` in `unitTesting.md`. - Clarify `tomlkit` installation requirement and fix no-argument command example in `updatingExistingAddons.md`.

test: add unit tests and documentation for .addonmergeignore

87372e5

- Add testSetupAddonMergeIgnore and testAddonMergeIgnore to test_syncAddonWithTemplate.py - Document both new tests in docs/unitTesting.md

abdel792 closed this Aug 5, 2026

abdel792 reopened this Aug 5, 2026

abdel792 marked this pull request as ready for review August 5, 2026 20:40

seanbudd reviewed Aug 6, 2026

View reviewed changes

seanbudd marked this pull request as draft August 6, 2026 01:45

tests(template): add missing trailing newline to test_syncAddonWithTe…

4cbab17

…mplate.py

docs: restore AddonTemplate URL casing and remove test suite details

57c1819

- Fix casing for AddonTemplate repository URL in updatingExistingAddons.md - Remove detailed syncAddonWithTemplate test suite breakdown in unitTesting.md to keep coverage in docstrings

abdel792 added 2 commits August 9, 2026 16:15

style(sync): add trailing empty line to some files

d6a6050

seanbudd reviewed Aug 10, 2026

View reviewed changes

Comment thread syncAddonTool/syncAddonTool.spec

seanbudd reviewed Aug 10, 2026

View reviewed changes

Comment thread syncAddonWithTemplate.py Outdated

seanbudd mentioned this pull request Aug 10, 2026

Add pull request templates #51

Draft

seanbudd reviewed Aug 10, 2026

View reviewed changes

Comment thread docs/managementFromGit/updatingExistingAddons.md Outdated

seanbudd marked this pull request as draft August 11, 2026 06:12

Update docs/managementFromGit/updatingExistingAddons.md to document

7c7b92e

the syncAddonTool workflow for syncing add-ons with AddonTemplate.

abdel792 marked this pull request as ready for review August 11, 2026 15:33

docs: remove invalid -m script syntax in syncAddonTool usage examples

9701532

Remove instances of `python -m syncAddonTool.py` from updatingExistingAddons.md to keep only valid module and directory execution syntaxes.

docs(cli): document -v/--verbose flag and refine debug logging

9abf590

- Add missing -v/--verbose flag to CLI options table in docs/managementFromGit/updatingExistingAddons.md. - Suppress redundant dependency decision logs when running with --verbose.

fix(logging): include full TOML section path in list merge debug logs

8f8694b

Prepend full TOML key path (e.g. tool.ruff.include) when logging list merges in pyproject.toml to eliminate ambiguity.

Merge branch 'master' into syncAddon

4319d23

Merge branch 'master' into syncAddon

557d209

seanbudd requested a balanced review from Copilot September 4, 2026 07:19

Copilot started reviewing on behalf of seanbudd September 4, 2026 07:20 View session

Copilot AI reviewed Sep 4, 2026

View reviewed changes

seanbudd reviewed Sep 4, 2026

View reviewed changes

seanbudd marked this pull request as draft September 4, 2026 09:33

		- Inside this file, list the names, relative paths, or glob patterns of the files or folders you want the tool to skip during synchronization.
		- The file uses standard `.gitignore` pattern matching syntax (parsed via `pathspec`).

Uh oh!

Conversation

abdel792 commented Aug 4, 2026

Link to issue number:

Summary of the issue:

Description of developer facing changes:

Description of development approach:

Testing strategy:

Known issues with pull request:

Code Review Checklist

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

abdel792 commented Aug 5, 2026

Uh oh!

abdel792 commented Aug 5, 2026

Uh oh!

abdel792 commented Aug 5, 2026

Uh oh!

abdel792 commented Aug 5, 2026

Uh oh!

abdel792 commented Aug 5, 2026

Uh oh!

Uh oh!

seanbudd Aug 6, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

abdel792 commented Aug 6, 2026

Uh oh!

abdel792 commented Aug 6, 2026

Uh oh!

abdel792 commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

abdel792 commented Aug 9, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

abdel792 commented Aug 10, 2026

Uh oh!

abdel792 commented Aug 11, 2026

Uh oh!

abdel792 commented Aug 11, 2026

Uh oh!

abdel792 commented Aug 11, 2026

Uh oh!

abdel792 commented Aug 12, 2026

Uh oh!

abdel792 commented Aug 12, 2026

Uh oh!

abdel792 commented Aug 13, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

🔵 Needs a closer look

Uh oh!

abdel792 commented Aug 6, 2026 •

edited

Loading