Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .env.example
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,4 @@ NEXT_PUBLIC_POSTHOG_HOST=
DATABASE_URL=

# RESEND API KEY FOR EMAILS
NEXT_PUBLIC_RESEND_API_KEY=
# NEXT_PUBLIC_RESEND_API_KEY=
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Add a blank line at the end of the file.

The file is missing a trailing newline, which is flagged by dotenv-linter. This is a minor formatting issue commonly addressed by adding a blank line at the end of the file.

🔎 Proposed fix
 # RESEND API KEY FOR EMAILS
-# NEXT_PUBLIC_RESEND_API_KEY=
+# NEXT_PUBLIC_RESEND_API_KEY=
📝 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
# NEXT_PUBLIC_RESEND_API_KEY=
# NEXT_PUBLIC_RESEND_API_KEY=
🧰 Tools
🪛 dotenv-linter (4.0.0)

[warning] 22-22: [EndingBlankLine] No blank line at the end of the file

(EndingBlankLine)

🤖 Prompt for AI Agents
In @.env.example around line 22, Add a trailing newline to the end of
.env.example so the file ends with a blank line (after the
"NEXT_PUBLIC_RESEND_API_KEY=" line); this satisfies dotenv-linter by ensuring
the file ends with a newline character.