Open
Conversation
Owner
4f345eb to
08298ac
Compare
Author
|
Thanks for the feedback! I've removed the rename commit from this PR. It should be clean now. |
shishir-21
approved these changes
Feb 7, 2026
Collaborator
shishir-21
left a comment
There was a problem hiding this comment.
Thankyou for this pr
I approved this pr
Ready to merge👍
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi! As requested, I have added the /health endpoint to server.js.
Changes:
Implemented GET /health which returns 200 OK and a timestamp.
Fix: Renamed .env.example: to .env.example.
Reason for the file rename: I am working on Windows, and the colon (:) in the filename prevented me from cloning and running the project locally. I had to rename it to make the environment work. I included this fix in this PR because I couldn't verify the /health endpoint without it.
I am aware there is an existing discussion regarding this in Issue #84