Update Deployments.md

[vero295]

🚀 StarShop Pull Request

Mark with an x all the checkboxes that apply (like [x])

• Closes Referral contract #138
• Added tests (if necessary)
• Run tests
• Run formatting
• Evidence attached
• Commented the code

---

📌 Type of Change

• Documentation (updates to README, docs, or comments)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

---

📝 Changes description

---

📸 Evidence (A photo is required as evidence)

---

⏰ Time spent breakdown

---

🌌 Comments

---

Thank you for contributing to StarShop, we are glad that you have chosen us as your project of choice and we hope that you continue to contribute to this great project, so that together we can make our mark at the top!

Summary by CodeRabbit

• Documentation
  • Updated deployment documentation to include a new “Referral contract” section with its contract ID for easy reference.
  • Provides a clear, authoritative source to locate and verify the Referral contract across environments.
  • No existing entries were modified.
  • Improves transparency for users integrating with or troubleshooting the Referral contract by centralizing key deployment details.

[coderabbitai]

Walkthrough

A new “Referral contract” entry was added to Deployments.md, including a header and a specific contract-id. No other files or existing entries were modified.

Changes

Cohort / File(s)	Summary
Docs: Deployments Deployments.md	Added “# Referral contract” section with contract-id CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update Deployments.md #148 — Also adds a new contract deployment entry to Deployments.md, similar documentation scope.

Suggested reviewers

• Villarley

Poem

I thump my paws in docs delight,
A contract hops into the light.
ID strings like carrot rows,
Testnet breezes ruffle those.
One more burrow on the map—
Deployments marked; nap-nap-nap. 🐇✨

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings, 1 inconclusive)

Check name	Status	Explanation	Resolution
Linked Issues Check	⚠️ Warning	While the PR correctly adds the new contract ID to DEPLOYMENTS.md as specified, it does not mark the deployment as test-only in the documentation and includes no evidence or verification of a successful Stellar Testnet deployment, so it fails to fully satisfy the acceptance criteria of issue #138.	Please update the documentation entry to indicate that this deployment is test-only and attach evidence or logs demonstrating that the referral contract was built and deployed successfully on the Stellar Testnet.
Description Check	⚠️ Warning	The pull request description includes the repository’s template but leaves every checklist item and descriptive section blank, providing no information on what was changed, why, or any evidence of validation, making it incomplete and not useful for reviewers.	Please fill in the template by checking the appropriate boxes, completing the “Changes description” section to explain what was done, adding any evidence of successful deployment, and providing a time-spent breakdown and comments as required.
Title Check	❓ Inconclusive	The title “Update Deployments.md” correctly references the file being modified but is too generic and does not convey that this change specifically adds a referral contract entry, so it does not clearly summarize the main content of the change.	Consider renaming the pull request to something more descriptive such as “Add referral contract entry to Deployments.md” to clearly communicate the primary change to reviewers.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Out of Scope Changes Check	✅ Passed	All modifications in this PR are confined to DEPLOYMENTS.md to add the referral contract entry, which directly aligns with the linked issue’s goals and does not introduce any unrelated code or documentation changes.
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

---

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

🧪 Early access (Sonnet 4.5): enabled

We are currently testing the Sonnet 4.5 model, which is expected to improve code review quality. However, this model may lead to increased noise levels in the review comments. Please disable the early access features if the noise level causes any inconvenience.

Note:

• Public repositories are always opted into early access features.
• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

Deployments.md (1)

26-26: Consider standardizing contract ID formatting.

The file has inconsistent formatting—some entries use backticks around contract IDs (lines 2, 4, 8) while others don't (lines 6, 10, 12, 14, 16, 18, 20, 22, 26). Consider standardizing for better readability, either by wrapping all contract IDs in backticks or removing them entirely.

Example with backticks (matching lines 2, 4, 8):

-Contract-id : CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB
+Contract-id: `CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB`

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 22e476d and 2e2d0ae.

📒 Files selected for processing (1)

• Deployments.md (1 hunks)

[coderabbitai]

⚠️ Potential issue | 🟠 Major

Mark deployment as test-only per acceptance criteria.

The acceptance criteria from issue #138 explicitly require marking this deployment as test-only in the documentation. The current entry does not indicate this is a testnet deployment.

Apply this diff to mark the deployment as test-only:

-# Referral contract
-Contract-id : CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB
+# Referral contract (Testnet - Test Only)
+Contract-id : CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB

📝 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

	# Referral contract
	Contract-id : CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB
	# Referral contract (Testnet - Test Only)
	Contract-id : CA5JNSXCEEUO7VDHHWDBP7NACP7RP7MPULA2I3EHDW4B5QTNIT44HLOB

🤖 Prompt for AI Agents

In Deployments.md around lines 25 to 26, the referral contract entry lacks the
required "test-only" designation; update the entry to explicitly mark this
deployment as test-only (for example add a "Test-only: true" or "Network:
testnet / test-only" label alongside the Contract-id) and ensure the wording
matches the project's documentation style and acceptance criteria #138 so it's
clear this is not a mainnet deployment.