added about pic + info

[ayanrasulova]

GitHub Issues addressed

• This PR added about information for ayan rasulova (engineering)

What I did

i added my picture to team-pfps, and then my info to team_info.json

Screenshots

• Before

• After

Testing

• A brief explanation of tests done/written or how reviewers can test your work

Questions/Discussions/Notes

Summary by CodeRabbit

• New Features
  • Added a new Engineering team member profile: Ayan Rasulova (Developer, Class of 2027).
  • The Team page now includes their name, role, class year, profile image, and GitHub link.
  • The updated roster displays this profile alongside existing engineers wherever the engineering team is shown, ensuring the team listing reflects current members.

[coderabbitai]

Walkthrough

Added a new engineer entry to tcf_website/views/team_info.json by appending Ayan Rasulova to the engineering_team array with specified name, role, class year, image filename, and GitHub handle.

Changes

Cohort / File(s)	Change Summary
Team data update tcf_website/views/team_info.json	Appended engineering_team member object: name "Ayan Rasulova", role "Developer", class "2027", img_filename "ENG_Ayan_Rasulova.jpg", github "ayanrasulova".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A new dev hops into our scene, hooray! 🐇
Ayan joins the warren, ready to play.
JSON fields aligned, neat and bright,
GitHub at the ready, code in sight.
With ears up high and commits in tow,
Our carrot-shaped roadmap’s set to grow.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "added about pic + info" succinctly and accurately reflects the main change in the PR — adding a profile picture and corresponding about/info entry. It is concise and directly related to the edits in team-pfps and team_info.json, so a reviewer can quickly understand the primary intent. Minor stylistic improvements (capitalization and replacing "+" with "and" or naming the member) could increase clarity but are optional.
Description Check	✅ Passed	The PR description follows the repository template structure and includes "GitHub Issues addressed", "What I did", and before/after screenshots, so it documents the primary changes. However, the "GitHub Issues addressed" section does not include an issue number or a "Closes #" statement and the "Testing" section remains the template placeholder with no actual test steps or reviewer instructions. Given the small scope and presence of screenshots and a clear "What I did" entry, the description is mostly complete but needs the missing testing details and an issue reference if applicable.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch about-ayan

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

tcf_website/views/team_info.json (1)

127-132: Fix key typo "role:" → "role" (breaks downstream consumers).

This object uses "role:" (with a colon in the key) instead of "role", which will likely omit the role in the UI or any code expecting the canonical key.

-    {
-      "name": "Kingsley Kim",
-      "role:": "Developer",
-      "class": "2026",
-      "img_filename": "ENG_Kingsley_Kim.jpg",
-      "github": "kingsleykimm"
-    },
+    {
+      "name": "Kingsley Kim",
+      "role": "Developer",
+      "class": "2026",
+      "img_filename": "ENG_Kingsley_Kim.jpg",
+      "github": "kingsleykimm"
+    },

🧹 Nitpick comments (1)

tcf_website/views/team_info.json (1)

263-269: Optional: confirm image format/casing conventions and ordering rules.

• Many entries mix .jpg/.JPG/.jpeg/.webp. If the build or CDN is case‑sensitive, standardize extensions to avoid cache misses.
• If the list is intended to be alphabetical or grouped, consider placing the new entry accordingly to minimize future diff churn.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e37a946 and 38d646a.

⛔ Files ignored due to path filters (1)

• tcf_website/static/about/team-pfps/ENG_Ayan_Rasulova.jpg is excluded by !**/*.jpg

📒 Files selected for processing (1)

• tcf_website/views/team_info.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: pylint
• GitHub Check: django

🔇 Additional comments (1)

tcf_website/views/team_info.json (1)

263-268: LGTM — JSON valid & image present.
jq validated tcf_website/views/team_info.json; image present at static/about/team-pfps/ENG_Ayan_Rasulova.jpg.