Skip to content

Conversation

@hassan254-prog
Copy link
Contributor

@hassan254-prog hassan254-prog commented Jan 16, 2026

Describe the problem and your solution

  • add support for procore

Add first-party Procore integration with post-connection enrichment

Introduces a new Procore provider entry with OAuth metadata, optional companyId configuration, branded assets, and navigation wiring. Adds a post-connection hook that populates companyId automatically after OAuth by calling /rest/v1.0/companies, and ships Quickstart/setup/connect documentation plus generated snippet content for the docs site.

Key Changes

• Registered procore in packages/providers/providers.yaml with OAuth endpoints, optional companyId connection config, retry semantics, docs links, and header templating.
• Implemented packages/server/lib/hooks/connection/providers/procore/post-connection.ts to backfill companyId when absent by proxying GET /rest/v1.0/companies and persisting the first company ID.
• Exported the new hook via packages/server/lib/hooks/connection/index.ts and added the Procore logo asset for the webapp gallery.
• Documented the integration through new Quickstart, setup, and connect guides plus generated snippet files and updated docs/docs.json navigation.

Affected Areas

• packages/providers/providers.yaml
• packages/server/lib/hooks/connection/providers/procore/post-connection.ts
• packages/server/lib/hooks/connection/index.ts
• docs/api-integrations/procore*.mdx
• docs/snippets/generated/procore/*.mdx
• packages/webapp/public/images/template-logos/procore.svg
• docs/docs.json


This summary was automatically generated by @propel-code-bot

@hassan254-prog hassan254-prog self-assigned this Jan 16, 2026
@my-senior-dev-pr-review
Copy link

my-senior-dev-pr-review bot commented Jan 16, 2026

🤖 My Senior Dev — Analysis Complete

👤 For @hassan254-prog

📁 Expert in docs (339 edits) • ⚡ 28th PR this month

View your contributor analytics →


📊 34 files reviewed • 2 need attention

⚠️ Needs Attention:

  • docs/api-integrations/procore.mdx — Documentation highlights sensitive data handling without proper security warnings.
  • docs/api-integrations/procore.mdx — Documentation could be improved for better maintainability and clarity.

🚀 Open Interactive Review →

The full interface unlocks features not available in GitHub:

  • 💬 AI Chat — Ask questions on any file, get context-aware answers
  • 🔍 Smart Hovers — See symbol definitions and usage without leaving the diff
  • 📚 Code Archeology — Understand how files evolved over time (/archeology)
  • 🎯 Learning Insights — See how this PR compares to similar changes

💬 Chat here: @my-senior-dev explain this change — or try @chaos-monkey @security-auditor @optimizer @skeptic @junior-dev

📖 View all 12 personas & slash commands

You can interact with me by mentioning @my-senior-dev in any comment:

In PR comments or on any line of code:

  • Ask questions about the code or PR
  • Request explanations of specific changes
  • Get suggestions for improvements

Slash commands:

  • /help — Show all available commands
  • /archeology — See the history and evolution of changed files
  • /profile — Performance analysis and suggestions
  • /expertise — Find who knows this code best
  • /personas — List all available AI personas

AI Personas (mention to get their perspective):

Persona Focus
@chaos-monkey 🐵 Edge cases & failure scenarios
@skeptic 🤨 Challenge assumptions
@optimizer Performance & efficiency
@security-auditor 🔒 Security vulnerabilities
@accessibility-advocate Inclusive design
@junior-dev 🌱 Simple explanations
@tech-debt-collector 💳 Code quality & shortcuts
@ux-champion 🎨 User experience
@devops-engineer 🚀 Deployment & scaling
@documentation-nazi 📚 Documentation gaps
@legacy-whisperer 🏛️ Working with existing code
@test-driven-purist Testing & TDD

For the best experience, view this PR on myseniordev.com — includes AI chat, file annotations, and interactive reviews.

@hassan254-prog hassan254-prog force-pushed the wari/add-support-for-procure branch from a0c56e5 to 1fb80d9 Compare January 16, 2026 13:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants