Skip to content

chore: Replace contact email with hi@ollin.sh#194

Merged
gocanto merged 1 commit into
mainfrom
chore/replace-contact-email
Jun 2, 2026
Merged

chore: Replace contact email with hi@ollin.sh#194
gocanto merged 1 commit into
mainfrom
chore/replace-contact-email

Conversation

@gocanto

@gocanto gocanto commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace gus@oullin.io with hi@ollin.sh in the profile fixture so the generated contact page surfaces the new address
  • Update the matching SEO generator test assertion to expect the new mailto: value

Test plan

  • go test ./metal/cli/seo/...
  • grep -rn "gus@oullin" . returns no results

Summary by CodeRabbit

Release Notes

  • Chores
    • Updated internal configuration and test data fixtures.

Note: This release contains primarily internal updates with minimal end-user impact.

Switches the profile fixture and matching SEO generator test
assertion from gus@oullin.io to hi@ollin.sh so the generated
contact page exposes the new address.
@coderabbitai

coderabbitai Bot commented Jun 2, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c831e760-fb3f-4789-8f41-abe4eccf8ae8

📥 Commits

Reviewing files that changed from the base of the PR and between 026342f and b8fbe8c.

📒 Files selected for processing (2)
  • metal/cli/seo/generator_test.go
  • storage/fixture/profile.json

Walkthrough

The PR updates the user's email address from gus@oullin.io to hi@ollin.sh across the test fixture and its corresponding assertion in the contact page generation test.

Changes

Email Address Update

Layer / File(s) Summary
Email fixture and contact page assertion
storage/fixture/profile.json, metal/cli/seo/generator_test.go
Profile fixture email is updated to hi@ollin.sh, and the test assertion verifying the generated contact page mailto link is updated to match.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • oullin/api#183: Both PRs update the same SEO contact-page test and profile fixture email value in sequence.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and accurately summarises the primary change: replacing a contact email address across the codebase.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


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

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the email address from 'gus@oullin.io' to 'hi@ollin.sh' in both the profile fixture and the SEO generator test. I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

@gocanto gocanto merged commit 24e8b72 into main Jun 2, 2026
4 checks passed
@gocanto gocanto deleted the chore/replace-contact-email branch June 2, 2026 05:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant