# GitLab logic verification, saved PR reviews, and accessibility settings > 8 updates: Logic verification for GitLab merge requests, Configure accessibility reporting per application, Choose an Azure DevOps repository in chat,… Source: https://qa.tech/changelog/2026-11-03 --- 8 updates shipped on November 3, 2026. In this release 1. 01[Logic verification for GitLab merge requests](#2026-11-03-gitlab-logic-verification)Highlight 2. 02[Configure accessibility reporting per application](#2026-11-03-accessibility-per-application) 3. 03[Choose an Azure DevOps repository in chat](#2026-11-03-azure-multiple-codebases) 4. 04[View invoices in billing](#2026-11-03-billing-invoice-list) 5. 05[Commit messages inform PR reviews](#2026-11-03-commit-messages-in-pr-reviews) 6. 06[Save PR reviews without posting comments](#2026-11-03-review-without-comments) 7. 07[Connect code later during setup](#2026-11-03-setup-code-later) 8. 08[Setup checks site access and sign-in options](#2026-11-03-setup-url-and-login-guidance) 1. Highlight Featured this release ## Logic verification for GitLab merge requests GitLab repository settings now include Logic Verification (beta) under Code Access. GitLab repository settings now include Logic Verification (beta) under Code Access. Enable it to check the logic of a merge request against the repository code, including repositories in subgroups. More on this: [PR testing](https://qa.tech/product/pr-testing) and [gitlab](https://qa.tech/product/integrations/gitlab). [\# Direct link](#2026-11-03-gitlab-logic-verification) 2. Update 02 of 08 ## Configure accessibility reporting per application Runs support accessibility reporting settings per application, including tags, disabled rules, incomplete results and iframe handling. Runs support accessibility reporting settings per application, including tags, disabled rules, incomplete results and iframe handling. App, scheduled and API runs enable reporting by default; quick chat and MCP runs leave it off unless explicitly enabled. More on this: [web testing](https://qa.tech/product/web-testing) and [accessibility testing](https://qa.tech/use-cases/accessibility-testing). [\# Direct link](#2026-11-03-accessibility-per-application) 3. Update 03 of 08 ## Choose an Azure DevOps repository in chat For projects with multiple mapped Azure DevOps repositories, specify a project and repository, a unique repository name or a repository URL in your codebase question. For projects with multiple mapped Azure DevOps repositories, specify a project and repository, a unique repository name or a repository URL in your codebase question. Chat uses the repository you identify. More on this: [integrations](https://qa.tech/product/integrations) and [PR testing](https://qa.tech/product/pr-testing). [\# Direct link](#2026-11-03-azure-multiple-codebases) 4. Update 04 of 08 ## View invoices in billing The billing Invoices tab lists invoice dates, numbers, amounts and statuses, with links to view each invoice and download its PDF. The billing Invoices tab lists invoice dates, numbers, amounts and statuses, with links to view each invoice and download its PDF. Paging lets you find older invoices in the same place. More on this: [pricing](https://qa.tech/pricing) and [product](https://qa.tech/product). [\# Direct link](#2026-11-03-billing-invoice-list) 5. Update 05 of 08 ## Commit messages inform PR reviews PR reviews and triage compare commit messages with the title, description and diff. PR reviews and triage compare commit messages with the title, description and diff. Follow-up reviews focus on newly added commits and note rewritten history. More on this: [PR testing](https://qa.tech/product/pr-testing) and [pr cicd testing](https://qa.tech/use-cases/pr-cicd-testing). [\# Direct link](#2026-11-03-commit-messages-in-pr-reviews) 6. Update 06 of 08 ## Save PR reviews without posting comments The change review API accepts disableReviewComments to save a review in QA.tech without posting comments, progress messages or approvals to the pull request. The change review API accepts disableReviewComments to save a review in QA.tech without posting comments, progress messages or approvals to the pull request. The check run is still written. Review cards show “Review saved, not posted” so teams can evaluate results before enabling comments. More on this: [PR testing](https://qa.tech/product/pr-testing) and [MCP](https://qa.tech/product/mcp). [\# Direct link](#2026-11-03-review-without-comments) 7. Update 07 of 08 ## Connect code later during setup Choose “Not now” when setup asks where your code lives to continue and add a todo for connecting it later. Choose “Not now” when setup asks where your code lives to continue and add a todo for connecting it later. Setup also offers a short questionnaire of areas with thin coverage when you ask it to generate tests without naming an area. More on this: [product](https://qa.tech/product) and [web testing](https://qa.tech/product/web-testing). [\# Direct link](#2026-11-03-setup-code-later) 8. Update 08 of 08 ## Setup checks site access and sign-in options The onboarding URL field checks whether your site is reachable and shows access guidance without blocking setup. The onboarding URL field checks whether your site is reachable and shows access guidance without blocking setup. For Google-only sign-in, chat explains the available testing options without requesting Google credentials. If your organization has no logo, setup can use the site icon without replacing an uploaded logo. More on this: [web testing](https://qa.tech/product/web-testing) and [product](https://qa.tech/product). [\# Direct link](#2026-11-03-setup-url-and-login-guidance) ## Your team moves fast. Can your testing keep up? Our QA agents test your product autonomously, so moving fast never means shipping broken. Start free or get a 30-minute demo. [Get started for free](https://app.qa.tech/auth/sign-up)[Book a demo](https://qa.tech/demo) [QA.tech](https://qa.tech/)[SOC 2 Type 2 compliant![Sensiba SOC 2 Type 2 compliant](https://qa.tech/assets/soc2-type2-badge-DPb1j9VX.png)](https://trust.qa.tech/) ### Product - [API Testing](https://qa.tech/product/api-testing) - [MCP](https://qa.tech/product/mcp) - [Mobile Testing](https://qa.tech/product/mobile-testing) - [PR Testing](https://qa.tech/product/pr-testing) - [Voice Testing](https://qa.tech/product/voice-testing) - [Web Testing](https://qa.tech/product/web-testing) - [AI QA testing guide](https://qa.tech/ai-qa-testing) - [Changelog](https://qa.tech/changelog) - [Integrations](https://qa.tech/product/integrations) - [Platform overview](https://qa.tech/product) - [Use cases](https://qa.tech/use-cases) ### Compare - [QA.tech vs Cypress](https://qa.tech/compare/qa-tech-vs-cypress) - [QA.tech vs Mabl](https://qa.tech/compare/qa-tech-vs-mabl) - [QA.tech vs Playwright](https://qa.tech/compare/qa-tech-vs-playwright) - [QA.tech vs QA Wolf](https://qa.tech/compare/qa-tech-vs-qa-wolf) - [B2B SaaS testing](https://qa.tech/saas) - [Ecommerce testing](https://qa.tech/industries/ecommerce) - [For CTOs](https://qa.tech/solutions/ctos) - [For QA teams](https://qa.tech/solutions/qa-testers) ### Resources - [Docs](https://docs.qa.tech/) - [Blog](https://qa.tech/blog) - [Events](https://qa.tech/events) - [Pricing](https://qa.tech/pricing) - [Case Studies](https://qa.tech/case-studies) ### Company - [About](https://qa.tech/about-us) - [Partner Program](https://qa.tech/partnerships) - [Press](https://qa.tech/press) - [Contact Us](https://qa.tech/contact) - [Privacy Policy](https://qa.tech/privacy-policy) - [Terms of Service](https://trust.qa.tech/resources?s=mb9w4yjb03i3t8bjsq4jx3&name=main-agreement.pdf) - [Trust Center: Security & Compliance](https://trust.qa.tech/) ### Social - [](https://www.linkedin.com/company/qa-tech-ai/) - [](https://x.com/getqatech) - [](https://www.instagram.com/getqatech/) © 2026 QA.tech. All rights reserved