docs(contributor): contributors readme action update

[github-actions]

📑 Description

Contributors readme action update

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

☢️ Does this introduce a breaking change?

• Yes
• No

---

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the contributors and bots sections in README.md by adjusting table markup and adding a new contributor entry to the collaborators list.

File-Level Changes

and tags to use tab-indented formatting instead of space-indented formatting in both contributors and bots tables.

Modify opening table markup so that

and are on the same indentation level, and closing and tags match the new structure.

Update closing table section so that rows end with a followed by a new

tag in both sections.

Change	Details	Files
Adjust HTML table structure and indentation for contributors and bots sections in README.	Switch table
README.md
Add a new collaborator entry to the contributors table.	Insert a new	cell in the contributors row for the GitHub user nimble-turtle with avatar image, profile link, and display name. Ensure the new collaborator appears alongside existing collaborators in the same table row.	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
progressbar	Ready	Preview, Comment	Apr 14, 2026 2:21pm

[deepsource-io]

DeepSource Code Review

We reviewed changes in edc9fb2...f6667b4 on this pull request. Below is the summary for the review, and you can see the individual issues we found as inline review comments.

See full review on DeepSource ↗

PR Report Card

Overall Grade

Security   Reliability   Complexity   Hygiene

Code Review Summary

Analyzer	Status	Updated (UTC)	Details
Secrets		Apr 14, 2026 2:21p.m.	Review ↗
Python		Apr 14, 2026 2:21p.m.	Review ↗

---

Important

AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.

[gstraccini]

Please provide a description for this pull request.

[codacy-production]

Not up to standards ⛔

🔴 Issues 7 minor

Alerts:
⚠ 7 issues (≤ 0 issues of at least minor severity)

Results:
7 new issues

Category	Results
BestPractice	3 minor
CodeStyle	4 minor

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[sourcery-ai]

Hey - I've left some high level feedback:

• The new <tbody> tags at the end of both tables replace closing tags with opening ones, which breaks the HTML structure; these should remain </tbody> to keep the markup valid.
• The change from space-based indentation to tabs within the table markup makes the README formatting inconsistent with the existing style; consider keeping indentation consistent with the rest of the file.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new `<tbody>` tags at the end of both tables replace closing tags with opening ones, which breaks the HTML structure; these should remain `</tbody>` to keep the markup valid.
- The change from space-based indentation to tabs within the table markup makes the README formatting inconsistent with the existing style; consider keeping indentation consistent with the rest of the file.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

2026-04-14T14:21:40Z INF scanning for exposed secrets...
2:21PM INF 131 commits scanned.
2026-04-14T14:21:40Z INF scan completed in 22.9ms
2026-04-14T14:21:40Z INF no leaks found