[PR #2790] [CLOSED] chore: update env copy instructions #4069

Closed
opened 2026-03-17 01:38:14 +03:00 by kerem · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/hoppscotch/hoppscotch/pull/2790
Author: @TheHollidayInn
Created: 10/16/2022
Status: Closed

Base: mainHead: chore/update-copy-env-readme


📝 Commits (1)

  • fe5dbfe chore: update env copy instructions

📊 Changes

1 file changed (+3 additions, -1 deletions)

View changed files

📝 README.md (+3 -1)

📄 Description

Closes #

Description

When following the current .env file instructions, this will lead you to have a removed .env.example which can accidentally be committed. So this is a minor change in the instructions.

Checks

  • My pull request adheres to the code style of this project
  • My code requires changes to the documentation
  • I have updated the documentation as required
  • All the tests have passed

Additional Information


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/hoppscotch/hoppscotch/pull/2790 **Author:** [@TheHollidayInn](https://github.com/TheHollidayInn) **Created:** 10/16/2022 **Status:** ❌ Closed **Base:** `main` ← **Head:** `chore/update-copy-env-readme` --- ### 📝 Commits (1) - [`fe5dbfe`](https://github.com/hoppscotch/hoppscotch/commit/fe5dbfe7ec92f62ddf3ac8806411912f80686889) chore: update env copy instructions ### 📊 Changes **1 file changed** (+3 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+3 -1) </details> ### 📄 Description <!-- Thanks for creating this pull request 🤗 Please make sure that the pull request is limited to one type (docs, feature, etc.) and keep it as small as possible. You can open multiple prs instead of opening a huge one. --> <!-- If this pull request closes an issue, please mention the issue number below --> Closes # <!-- Issue # here --> ### Description <!-- Add a brief description of the pull request --> When following the current .env file instructions, this will lead you to have a removed .env.example which can accidentally be committed. So this is a minor change in the instructions. <!-- You can also choose to add a list of changes and if they have been completed or not by using the markdown to-do list syntax - [ ] Not Completed - [x] Completed --> ### Checks <!-- Make sure your pull request passes the CI checks and do check the following fields as needed - --> - [x] My pull request adheres to the code style of this project - [x] My code requires changes to the documentation - [x] I have updated the documentation as required - [x] All the tests have passed ### Additional Information <!-- Any additional information like breaking changes, dependencies added, screenshots, comparisons between new and old behaviour, etc. --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
kerem 2026-03-17 01:38:14 +03:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hoppscotch#4069
No description provided.