fix(schemas): allow spaces in Azure DevOps project and repo names#1170
fix(schemas): allow spaces in Azure DevOps project and repo names#1170brendan-kellam merged 3 commits intomainfrom
Conversation
Update the regex patterns for `projects` and `repos` in the Azure DevOps connection schema to accept names containing spaces. Azure DevOps natively supports spaces in project and repository names, but the previous pattern `[\w.-]+` excluded them. The org segment keeps its original restriction since Azure DevOps organization names are URL-based and don't support spaces. Fixes #1166 Co-authored-by: Brendan Kellam <brendan-kellam@users.noreply.github.com>
This comment has been minimized.
This comment has been minimized.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe PR relaxes Azure DevOps schema regexes to allow spaces in project and repository name segments by changing ChangesAzure DevOps Schema Validation Pattern Update
🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
@claude add a changelog |
|
Claude finished @brendan-kellam's task in 41s —— View job Changelog Added
Added a |
Co-authored-by: Brendan Kellam <brendan-kellam@users.noreply.github.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@schemas/v3/azuredevops.json`:
- Line 56: The current pattern string "^[\\w.-]+\\/[\\w. -]+$" allows leading or
trailing spaces in the project/repo segments; replace that pattern with a
stricter regex that requires each segment to start and end with a non-space
character (e.g., begin with a word/digit/dot/hyphen and disallow
leading/trailing spaces) so names like " My Project" or "My Project " are
rejected, and apply the same replacement to the other identical pattern
occurrence in the file.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 154889cd-bb02-41e0-a989-0121a1e785ec
📒 Files selected for processing (3)
docs/snippets/schemas/v3/azuredevops.schema.mdxpackages/schemas/src/v3/azuredevops.schema.tsschemas/v3/azuredevops.json
Update the regex patterns for
projectsandreposin the Azure DevOps connection schema to accept names containing spaces. Azure DevOps natively supports spaces in project and repository names, but the previous pattern[\w.-]+excluded them.Fixes #1166
Generated with Claude Code
Summary by CodeRabbit