Skip to content

Update README.md#882

Open
timtronic477 wants to merge 1 commit intosfbrigade:developfrom
timtronic477:patch-2
Open

Update README.md#882
timtronic477 wants to merge 1 commit intosfbrigade:developfrom
timtronic477:patch-2

Conversation

@timtronic477
Copy link
Copy Markdown

Updated README to include guidance for team members to use a different link.

Description

Updated the README file to include a note about using https://datasci-earthquake-omega.vercel.app/ to help with datasci team collecting data on users

Type of changes

  • ( ) Bugfix
  • (x) Chore
  • ( ) New Feature

Testing

  • ( ) I added automated tests
  • (x) I think tests are unnecessary

How to test

testing description here: i.e. run app, go to x page, see that it does y

Clean commits

  • ( ) I plan to Squash and Merge
  • ( ) My commit history is clean¹
    ¹ described here

Updated README to include guidance for team members to use a different link.
@vercel
Copy link
Copy Markdown

vercel bot commented Mar 27, 2026

@timtronic477 is attempting to deploy a commit to the SF Civic Tech - DS Working Group's projects Team on Vercel.

A member of the Team first needs to authorize it.

Copy link
Copy Markdown
Contributor

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

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 README.md to include a warning for team members to use the development environment for internal testing to avoid skewing production analytics. Review feedback highlights a potential inconsistency with other parts of the documentation regarding the development URL and suggests using more descriptive link text for better readability.

Comment on lines +7 to +18
## ⚠️ Important: Use the Development Site for Internal Testing

When browsing, testing, or reviewing the site as a team member, always use the development version:

**[datasci-earthquake-omega.vercel.app](https://datasci-earthquake-omega.vercel.app)**

Do **not** use the production site (`safehome.report`) for internal browsing or QA.
All user interactions — including page views and clicks — are tracked via PostHog.
Visiting production inflates our analytics and skews the data we report out.

> If you're unsure which environment to use, default to dev.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

While adding this guidance is helpful, it introduces a potential inconsistency in the documentation. This new section states that datasci-earthquake-omega.vercel.app is the development version to be used for internal testing. However, further down in the 'Production deployments' section (lines 615 and 620-624), https://develop.safehome.report is mentioned as the dev testing site deployed from the develop branch.

To avoid confusion for developers, could you please clarify the relationship between these two URLs in the README? For example:

  • Are they for different purposes?
  • Is one an alias for the other?
  • Should the older reference to develop.safehome.report be updated or removed?

Making this consistent will ensure all team members use the correct environment.


When browsing, testing, or reviewing the site as a team member, always use the development version:

**[datasci-earthquake-omega.vercel.app](https://datasci-earthquake-omega.vercel.app)**
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

For better readability, consider using a more descriptive link text instead of the full URL. This makes the link's purpose clearer at a glance.

Suggested change
**[datasci-earthquake-omega.vercel.app](https://datasci-earthquake-omega.vercel.app)**
**[Development Site](https://datasci-earthquake-omega.vercel.app)**

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