-
Notifications
You must be signed in to change notification settings - Fork 223
chore(profile): add Curtis M-Dillon profile #651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…l_name and github_trial_issue_link key-value pairs
WalkthroughUpdated Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
🚥 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
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. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
profile-submission.json (1)
3-7: Inconsistent indentation for thejediDeanentry
The indent levels here (8 spaces for{and 12 for keys) don’t match the rest of the file, which uses 4 spaces for objects and 6 for their properties. Please align this block to use 4-space indents for{and 6-space indents for the keys.Apply this diff to normalize the indentation:
@@ lines 3-7 - { - "github_handle": "jediDean", - "full_name": "Jesse Dean", - "github_trial_issue_link": "https://github.com/holdex/trial/issues/364" - }, + { + "github_handle": "jediDean", + "full_name": "Jesse Dean", + "github_trial_issue_link": "https://github.com/holdex/trial/issues/364" + },
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
profile-submission.json(2 hunks)
🔇 Additional comments (1)
profile-submission.json (1)
237-241: New profile entry forcmdillonlooks good
The object is appended with the correct keys, values, and comma placement. JSON structure is valid and consistent with existing entries.
Time Submission Status
|
tiffmyaaw
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost. Please rename your PR title and description based on our Guidelines
PR description to link your issue manually should be the one in the same repo, not the other.
Follow this instruction to verify past commits
Last, don't forget to update your time spent on the PR Time Tracker bot.
Feel free to look at the successfully closed PRs in this repo for refs.
…l_name and github_trial_issue_link key-value pairs
Signed-off-by: Tiffany V. Y. <116727382+tiffmyaaw@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
profile-submission.json(2 hunks)
🔇 Additional comments (2)
profile-submission.json (2)
443-447: cmdillon entry is correctly formatted and aligns with PR objective.The addition of Curtis Matthiesen-Dillon's profile is accurate:
- GitHub handle:
cmdillon✓- Full name:
Curtis Matthiesen-Dillon✓- Issue reference:
#648✓- JSON structure and syntax are valid ✓
1-679: Critical: File contains multiple duplicate profile entries.Scanning the file reveals several duplicate profiles that degrade data quality:
jediDean: appears at lines 4–7 and lines 104–107lucky-ivanius: appears at lines 9–12 and lines 154–1570xcoreblock: appears at lines 224–227 and lines 654–657roars2121: appears at lines 449–452 and lines 459–462agung-setiawan: appears at lines 549–552 and lines 564–567These duplicates should be removed. If this file is manually maintained, consider adding a merge-check or validation step to prevent future duplicates.
Should these duplicates be deduplicated as part of this PR, or in a separate issue?
Signed-off-by: Tiffany V. Y. <116727382+tiffmyaaw@users.noreply.github.com>
Removed entry for Jesse Dean from profile submissions. Signed-off-by: Tiffany V. Y. <116727382+tiffmyaaw@users.noreply.github.com>
Signed-off-by: Tiffany V. Y. <116727382+tiffmyaaw@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@profile-submission.json`:
- Around line 493-500: The profile entry uses an array for
github_trial_issue_link while the schema and other entries expect a string;
change the github_trial_issue_link value in this profile to a single string
(pick one canonical issue URL) so it matches the existing schema, or if you
intend to support arrays update the global schema and all consumers accordingly;
locate the github_trial_issue_link field in the profile-submission.json entry
for "Shantanu Swami" and convert the array to a single string to keep types
consistent with other entries.
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
profile-submission.json
🔇 Additional comments (2)
profile-submission.json (2)
3-7: Unrelated change to PR scope.This PR is for adding
cmdillon(issue#648), but this addsjediDean(issue#364). If intentional, consider a separate PR or update the PR description.
489-491: LGTM.Profile entry for
cmdilloncorrectly added with issue#648link as intended.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
| { | ||
| "github_handle": "jaibhedia", | ||
| "full_name": "Shantanu Swami", | ||
| "github_trial_issue_link": "https://github.com/holdex/trial/issues/680" | ||
| }, | ||
| { | ||
| "github_handle": "roars2121", | ||
| "full_name": "Ruairidh Orr Ewing", | ||
| "github_trial_issue_link": "https://github.com/holdex/trial/issues/645" | ||
| "github_trial_issue_link": [ | ||
| "https://github.com/holdex/trial/issues/679", | ||
| "https://github.com/holdex/trial/issues/680" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Schema inconsistency: array vs string.
github_trial_issue_link is an array here but a string everywhere else. This could break consumers expecting a consistent type.
Either:
- Keep it as a string (pick one issue), or
- Update the schema definition and all consumers to handle both types
Also, this change is unrelated to the PR objective (adding cmdillon).
🤖 Prompt for AI Agents
In `@profile-submission.json` around lines 493 - 500, The profile entry uses an
array for github_trial_issue_link while the schema and other entries expect a
string; change the github_trial_issue_link value in this profile to a single
string (pick one canonical issue URL) so it matches the existing schema, or if
you intend to support arrays update the global schema and all consumers
accordingly; locate the github_trial_issue_link field in the
profile-submission.json entry for "Shantanu Swami" and convert the array to a
single string to keep types consistent with other entries.
Signed-off-by: George Ciubotaru <george@holdex.io>
|
@cmdillon, @tiffmyaaw There are more changes than requested, please resolve the conflicts |
Signed-off-by: George Ciubotaru <george@holdex.io>
Adds my profile to
profile-submission.jsonfor the Product Designer role.Closes #648
Summary by CodeRabbit
New Features
Changes
✏️ Tip: You can customize this high-level summary in your review settings.