This repository was archived by the owner on Feb 18, 2026. It is now read-only.
Open
Conversation
# Conflicts: # app/dashboard/page.tsx
Contributor
Author
|
@Sree14hari Can you please check and approve too if all ok? |
Member
|
@gitit24x7 it have merge conflicts |
31cd69d to
fa06bda
Compare
Contributor
Author
|
@Sree14hari conflicts resolved. Please check now |
Member
|
@gitit24x7 conflicts |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I've added a simple Health Check endpoint at
/api/health.This is super useful for setting up uptime monitors (like UptimeRobot or Railway) to make sure our backend is alive and kicking. The response is lightweight and runs on the edge, so it's really fast and won't slow anything down.
You can test it here:
GET /api/healthIt returns a JSON object like this:
{ "status": "ok", "version": "0.1.0", "uptime": 123.45 } closes #406