Skip to content

Remove useless pictures and add .env.examples#2

Open
ye-spencer wants to merge 2 commits intomainfrom
remove_unused_files
Open

Remove useless pictures and add .env.examples#2
ye-spencer wants to merge 2 commits intomainfrom
remove_unused_files

Conversation

@ye-spencer
Copy link
Owner

No description provided.

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR performs cleanup tasks across the LittleFireExperiments projects by removing unused boilerplate files from Next.js applications and adding environment variable examples. The changes mark two TODO items as complete: removing unused files and adding .env.examples.

  • Removes standard Next.js boilerplate SVG files (next.svg, vercel.svg, globe.svg, window.svg, file.svg) from all three experiment projects
  • Adds .env.example files to each project with the shared LFE_WFIS_DATABASE_URL configuration
  • Updates .gitignore files to allow .env.example to be committed while still ignoring .env
  • Corrects a spelling error in TODO.md and marks cleanup tasks as complete

Reviewed changes

Copilot reviewed 10 out of 34 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
TODO.md Corrects spelling error ("reppo" → "repo") and marks cleanup tasks as completed
LittleFireExperiments/WhichTool/which-tool-is-good/.gitignore Changes pattern from .env* to .env to allow .env.example to be tracked
LittleFireExperiments/WhichTool/which-tool-is-good/.env.example Adds database URL environment variable example
LittleFireExperiments/WhichTool/which-tool-is-good/public/*.svg Removes unused Next.js boilerplate SVG files
LittleFireExperiments/StatementAgree/agree-or-disagree/.gitignore Changes pattern from .env* to .env to allow .env.example to be tracked
LittleFireExperiments/StatementAgree/agree-or-disagree/.env.example Adds database URL environment variable example
LittleFireExperiments/StatementAgree/agree-or-disagree/public/*.svg Removes unused Next.js boilerplate SVG files
LittleFireExperiments/MagicReal/what-makes-magic-real/whatMakesMagicReal.csv Removes data file from project root
LittleFireExperiments/MagicReal/what-makes-magic-real/.gitignore Changes pattern from .env* to .env to allow .env.example to be tracked
LittleFireExperiments/MagicReal/what-makes-magic-real/.env.example Adds database URL environment variable example
LittleFireExperiments/MagicReal/what-makes-magic-real/public/*.svg Removes unused Next.js boilerplate SVG files
LittleFireExperiments/GoodFood/which-food-is-good/.gitignore Changes pattern from .env* to .env to allow .env.example to be tracked
LittleFireExperiments/GoodFood/which-food-is-good/.env.example Adds database URL environment variable example
LittleFireExperiments/GoodFood/which-food-is-good/public/*.svg Removes unused Next.js boilerplate SVG files

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.


# env files (can opt-in for committing if needed)
.env*
.env
Copy link

Copilot AI Dec 3, 2025

Choose a reason for hiding this comment

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

Changing .gitignore to only ignore .env (from the more comprehensive .env*) can lead to accidental commits of environment-specific files like .env.local, .env.production, and .env.development, leaking secrets stored in those files. An attacker accessing the repository or its history could obtain database credentials, API keys, or other sensitive configuration. Revert to ignoring all env variants (e.g., use .env*) or explicitly ignore known patterns:

.env
.env.*
.env.local
.env.development
.env.production
.env.test
Suggested change
.env
.env
.env.*
.env.local
.env.development
.env.production
.env.test

Copilot uses AI. Check for mistakes.

# env files (can opt-in for committing if needed)
.env*
.env
Copy link

Copilot AI Dec 3, 2025

Choose a reason for hiding this comment

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

Changing .gitignore to only ignore .env (from .env*) increases the risk of committing environment-specific files (e.g., .env.local, .env.production), exposing secrets like API keys and database URLs. If these files are pushed to VCS, attackers with repo access can retrieve sensitive credentials. Revert to .env* or explicitly ignore common variants:

.env
.env.*
.env.local
.env.development
.env.production
.env.test
Suggested change
.env
.env
.env.*
.env.local
.env.development
.env.production
.env.test

Copilot uses AI. Check for mistakes.

# env files (can opt-in for committing if needed)
.env*
.env
Copy link

Copilot AI Dec 3, 2025

Choose a reason for hiding this comment

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

Narrowing .gitignore from .env* to .env can result in environment-specific files (e.g., .env.local, .env.production) being tracked and committed, leaking secrets within those files. Anyone with repo or commit history access could obtain credentials and sensitive configuration. Restore ignoring all env variants (use .env*) or ignore explicit patterns like:

.env
.env.*
.env.local
.env.development
.env.production
.env.test
Suggested change
.env
.env
.env.*
.env.local
.env.development
.env.production
.env.test

Copilot uses AI. Check for mistakes.

# env files (can opt-in for committing if needed)
.env*
.env
Copy link

Copilot AI Dec 3, 2025

Choose a reason for hiding this comment

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

Restricting .gitignore to only .env (instead of .env*) risks committing files like .env.local, .env.production, and .env.development with secrets. Attackers with access to the repository or its history could extract sensitive credentials. Revert to .env* or add explicit ignore patterns:

.env
.env.*
.env.local
.env.development
.env.production
.env.test
Suggested change
.env
.env
.env.*
.env.local
.env.development
.env.production
.env.test

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments