chore: Add profile to profile-submission.json

[geshtng]

This PR closes #88

Add profile to profile-submission.json

Summary by CodeRabbit

• New Features

  • Introduced a new team profile entry listing Gerald Bendryandre Sihotang’s details, including a GitHub handle and an issue link for trial information.

• Chores

  • Updated .gitignore to include a new entry for ignoring .qodo files.

[coderabbitai]

Walkthrough

The update modifies the profile-submission.json file by adding a new team profile entry within the team_profiles array. The new entry includes the properties github_handle, full_name, and github_trial_issue_link for the team member "Gerald Bendryandre Sihotang" (GitHub handle "geshtng"). Additionally, there is a minor formatting change: the file now does not end with a newline.

Changes

File	Change Summary
profile-submission.json	Added a new team profile entry for Gerald Bendryandre Sihotang with properties: github_handle, full_name, and github_trial_issue_link. Also, noted the absence of a newline at the end of the file.
.gitignore	Added a new entry .qodo to ignore files or directories matching this pattern.

Possibly related PRs

• chore(profile): Add profile entry for Rayen Dhmaied #132: The changes in the main PR involve adding a new team profile entry in the same team_profiles array of profile-submission.json as the retrieved PR, which also adds a profile entry, indicating a direct modification to the same structure.
• chore(profile): add profile for Shadab Khan #79: The changes in the main PR and the retrieved PR both involve adding new entries to the team_profiles array in the profile-submission.json file, indicating a direct relationship at the code level.
• chore(profile): update team profiles #122: The changes in the main PR and the retrieved PR both involve the addition of new team profile entries in the profile-submission.json file, indicating a direct relationship at the code level.

Suggested reviewers

• zolotokrylin

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 76e880a and 63213b0.

📒 Files selected for processing (1)

• profile-submission.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• profile-submission.json

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

profile-submission.json (1)

14-14: Missing Trailing Newline

The file currently does not end with a newline. It's generally best practice to include a trailing newline for compatibility with various tools and editors.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between db1c4ce and 97d44d8.

📒 Files selected for processing (1)

• profile-submission.json (1 hunks)

🔇 Additional comments (1)

profile-submission.json (1)

7-11: New Profile Entry Added Correctly

The JSON entry for "geshtng" is correctly inserted into the team_profiles array with all required keys (github_handle, full_name, github_trial_issue_link) present. This aligns with the PR objective.

[tiffmyaaw]

@geshtng please resolve conflicts and request review from me. Btw, for one issue, we use closes instead of resolves, read again

[tiffmyaaw]

@geshtng it still has conflicts