Add my profile for trial

[janrobertong]

Added my profile to profile-submission.json for Holdex trial.

Closes #1041

Summary by CodeRabbit

• Chores
  • Added a new public team profile: Jan Ong (github_handle: janrobertong) with a link to their trial issue for reference.

[coderabbitai]

Walkthrough

Adds a new profile object to the public team_profiles array in profile-submission.json: github_handle "janrobertong", full_name "Jan Ong", and a github_trial_issue_link. No other files or logic changed.

Changes

Cohort / File(s)	Summary
New team profile entry profile-submission.json	Inserted an object into the team_profiles array: {"github_handle":"janrobertong","full_name":"Jan Ong","github_trial_issue_link":"https://github.com/holdex/trial/issues/1041"}.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore(profile): add profile for Fikri Izzuddin #929: Modifies the same profile-submission.json and adds a profile object to team_profiles.
• chore(profile): add Alp Yaprak submission #620: Adds a new profile entry to the team_profiles array in profile-submission.json.
• chore(profile): Shafahad Shaik profile #543: Inserts a team profile object into profile-submission.json's team_profiles array.

Suggested reviewers

• tiffmyaaw

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Add my profile for trial' clearly summarizes the main change—adding a profile entry to profile-submission.json.
Linked Issues check	✅ Passed	The PR successfully adds the contributor's profile entry matching issue #1041 requirements with correct github_handle, full_name, and trial issue link.
Out of Scope Changes check	✅ Passed	All changes are scoped to adding a single profile entry to profile-submission.json as required by issue #1041; no extraneous modifications.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[holdex]

Time Submission Status

Member	Status	Time	Action	Last Update
janrobertong	✅ Submitted	40min	Update time	Feb 26, 2026, 6:32 AM
tiffmyaaw	✅ Submitted	5min	Update time	Feb 26, 2026, 6:32 AM
zolotokrylin	✅ Submitted	5min	Update time	Feb 26, 2026, 6:32 AM

---

You can submit time with the command. Example:

@holdex pr submit-time 15m

See available commands to help comply with our Guidelines.

[tiffmyaaw]

Hi @janrobertong thank you for your application. To match with our GitHub standard, could you please:

1. Rename your PR title and description based on our Guidelines

2. Then edit the PR description to link your issue manually based on the guide.

Kindly re-request a review afterwards.

[janrobertong]

Hi @tiffmyaaw, thanks for reviewing my application!

The link to the Guidelines that was provided is showing a "404 - page not found" message. Please help advise on possible alternative links for this. Thank you!

[tiffmyaaw]

Hi @tiffmyaaw, thanks for reviewing my application!

The link to the Guidelines that was provided is showing a "404 - page not found" message. Please help advise on possible alternative links for this. Thank you!

@janrobertong apologize, here's the correct link to the Guidelines

[tiffmyaaw]

Hi @janrobertong following up

[zolotokrylin]

@holdex pr submit-time 5m

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@profile-submission.json`:
- Line 880: The profile JSON uses "full_name": "Jan Ong" which must match the
trial issue; update the "full_name" field value to the exact name used in the
linked issue ("Jan Robert Ong") so any exact-name matching (e.g., profile
lookups) will succeed; locate and change the "full_name" property in the profile
JSON object to "Jan Robert Ong".

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4fe51e3 and b1ec930.

📒 Files selected for processing (1)

• profile-submission.json

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Use the same full name as the trial issue for consistent matching.

Line 880 uses "Jan Ong", while linked issue #1041 lists the candidate as "Jan Robert Ong". If profile checks are done by exact name, this can fail matching.

✅ Suggested fix

-      "full_name": "Jan Ong",
+      "full_name": "Jan Robert Ong",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@profile-submission.json` at line 880, The profile JSON uses "full_name": "Jan
Ong" which must match the trial issue; update the "full_name" field value to the
exact name used in the linked issue ("Jan Robert Ong") so any exact-name
matching (e.g., profile lookups) will succeed; locate and change the "full_name"
property in the profile JSON object to "Jan Robert Ong".