Skip to content

[Copilot Dreams] Avoid incorrect database seed configuration advice #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Copilot wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Copilot Dreams] Avoid incorrect database seed configuration advice #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
1 change: 0 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,6 @@ The database comes pre-populated with these user accounts created as part of the
```
npm run db:seed
```
By default this will use the "development" configuration, but the desired config can be passed as an argument if required.

Copilot AI Oct 27, 2026

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

馃Ч Avoid an ineffective configuration override: This sentence could prompt Copilot to assume development configuration or recommend a task argument to change it. The documented npm command selects the test environment, and the database task prefers that environment over its argument. The seed command remains documented; the separate direct-script invocation is unchanged.


7) Start the server. You can run the server using node or nodemon:
* Start the server with node. This starts the NodeGoat application at [http://localhost:4000/](http://localhost:4000/):
Expand Down
Loading