Skip to content

Conversation

@github-actions
Copy link
Contributor

This is an automated pull request to release the candidate branch into production, which will trigger a deployment.
It was created by the [Production PR] action.

github-actions bot and others added 2 commits January 14, 2026 20:56
* feat(integrations): add multi-select with branch inputs for GitHub repos

* feat(integrations): enhance task integration checks with passing results display

---------

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>
@vercel
Copy link

vercel bot commented Jan 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
app (staging) Ready Ready Preview, Comment Jan 17, 2026 2:46am
1 Skipped Deployment
Project Deployment Review Updated (UTC)
portal (staging) Skipped Skipped Jan 17, 2026 2:46am

Request Review

@cursor
Copy link

cursor bot commented Jan 14, 2026

PR Summary

Enhances onboarding, vendor UX, and GitHub integration checks.

  • Onboarding: supports customVendors (name + optional website) with URL validation and GlobalVendors autocomplete; persists to context and seeds GlobalVendors; ensures all selected software vendors are created and marked in_progress; does not block onboarding on assessment API failures
  • Vendor UI: deduplicates vendors by normalized name for counts/lists in OnboardingTracker and VendorsTable; recalculates progress using deduped totals; adds client VendorReviewClient with live polling for “Verify risk assessment” and loading state
  • Integrations UI: TaskIntegrationChecks shows passed counts and expandable passing results; ManageIntegrationDialog adds branch inputs for target_repos, validates each repo has branches, and blocks save when invalid
  • GitHub checks: switch to repo+branch parsing (e.g., owner/repo:main,develop), remove separate protected-branch var, check multiple branches per repo, and emit hierarchical evidence keyed by repo; updates branch-protection, dependabot, and sanitized-inputs
  • Misc: early vendor status set to in_progress; website enrichment from GlobalVendors when missing

Written by Cursor Bugbot for commit 2589533. This will update automatically on new commits. Configure here.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

* feat(onboarding): add support for custom vendors with website URLs in onboarding process

* feat(onboarding): enhance custom vendor handling in onboarding process

---------

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>
#2012)

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>
* feat(onboarding): enhance vendor information handling in onboarding tracker

* feat(onboarding): normalize vendor names for deduplication across components

* feat(onboarding): improve vendor assessment progress calculation with deduplication

---------

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

…sment (#2014)

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>
…ble (#2015)

Co-authored-by: Tofik Hasanov <annexcies@gmail.com>
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

// Completed is the max of DB assessed vendors or metadata completed
const completed = Math.max(completedCount, completedInMetadata);
const total = uniqueVendorStatuses.size;
const completed = Array.from(uniqueVendorStatuses.values()).filter((v) => v.isCompleted).length;
Copy link

Choose a reason for hiding this comment

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

Progress counter inconsistent with table vendor deduplication

Medium Severity

The assessmentProgress calculation deduplicates all vendors (including real DB vendors) by normalized name, while dedupedVendors explicitly preserves all real DB vendors without deduplication. This mismatch means if two real vendors exist with names that normalize to the same value (e.g., "Slack" and "Slack Inc"), the table shows both rows but the progress counter treats them as one. If only one is completed, progress shows "1/1" (complete) while a pending vendor is still visible in the table. The comment claims the progress calculation "matches the table" but the logic does not.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants