Added Omkar to contributors

[OmkarTipugade]

Fixes # .

Changes proposed in this pull request:

@pgRouting/admins

Summary by CodeRabbit

• Documentation
  • Enhanced the release documentation by adding Omkar Tipugade as a contributor.
  • Expanded the comprehensive list of past and present contributors to better recognize valuable participation in the project.

[coderabbitai]

Walkthrough

The pull request updates the documentation for pgRouting by modifying the file doc/src/pgRouting-introduction.rst. The changes add "Omkar Tipugade" under the "This Release Contributors" section and expand the list of contributors in the "Contributors Past & Present" section. The corporate sponsors section remains unchanged. There are no modifications to functionality or control flow.

Changes

File	Change Summary
doc/.../pgRouting-introduction.rst	Added "Omkar Tipugade" to the "This Release Contributors" section; expanded the "Contributors Past & Present" list with additional contributor names.

Poem

I'm a happy rabbit with a joyful leap,
Hopping through docs where new names now gleam so deep.
"Omkar Tipugade" and friends join our burrow of lore,
A trail of acknowledgments, a banner to explore.
With each added name, our story sings anew—
In the fields of code, every rabbit hops true!

---

📜 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 056d400 and e243a03.

📒 Files selected for processing (1)

• doc/src/pgRouting-introduction.rst (1 hunks)

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

• doc/src/pgRouting-introduction.rst

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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: 1

🔭 Outside diff range comments (2)

doc/src/pgRouting-introduction.rst (2)

74-75: ⚠️ Potential issue

Add Omkar to "This Release Contributors" section.

Since this PR is about adding Omkar as a contributor, the name should be included in the alphabetical list of contributors for this release.

 Regina Obe,
+Omkar Tipugade,
 Vicky Vergara

---

100-155: ⚠️ Potential issue

Add Omkar to "Contributors Past & Present" section.

The name should also be added to the comprehensive list of contributors in alphabetical order.

 Nitish Chauhan,
+Omkar Tipugade,
 Rajat Shinde,

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 95d26cf and 056d400.

📒 Files selected for processing (1)

• doc/src/pgRouting-introduction.rst (1 hunks)

🔇 Additional comments (1)

doc/src/pgRouting-introduction.rst (1)

63-155: Verify the spelling of the contributor's name.

There seems to be an inconsistency in the spelling of the contributor's name:

• PR username: "OmkarTipugade"
• Current addition: "Omkar Tipugae"

Please verify the correct spelling to ensure consistency.

[coderabbitai]

⚠️ Potential issue

Remove misplaced contributor entry.

The contributor name "Omkar Tipugae" is incorrectly placed outside of any contributor section. It should be moved to the appropriate sections.

-Omkar Tipugae
-

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

Omkar Tipugae