Add .env example and ignores

[AmagiDDmxh]

No description provided.

[follow-reviewer-bot]

Thank you for your contribution. We will review it promptly.

[follow-reviewer-bot]

@AmagiDDmxh, please use Conventional Commits format for your PR title.

Your PR title should follow this format:
<type>(<scope>): <description>

Common types include:

• feat: A new feature
• fix: A bug fix
• docs: Documentation changes
• style: Code style changes (formatting, missing semi colons, etc)
• refactor: Code refactoring
• test: Adding or updating tests
• chore: Changes to build process or auxiliary tools

Examples:

• feat(user): add user login function
• fix(api): correct HTTP response status code
• docs(readme): update installation guide

For more details, please visit: https://www.conventionalcommits.org/

[follow-reviewer-bot]

Suggested PR Title:

feat: add .env.example and update .gitignore patterns

Change Summary:
Added .env.example for environment variable configuration and updated .gitignore to include additional patterns to ignore temporary and build files while excluding .env.example from being ignored.

Code Review:

Code Review

Issues Requiring Change Requests:

1. File: .env.example

Lines: 1-8

• Issue: Sensitive placeholders should include comments explaining the required formatting. For example, PRIVATE_KEY may require specific formatting or delimiters that the developer should be aware of.
• Change Request: Add comments above each variable or as inline comments to clarify the expected values. Example:

  # Provide your OpenAI API key (string format).
  OPENAI_API_KEY=
  
  # Base URL for the OpenAI API service endpoint.
  ENDPOINT=
  
  # GitHub App details: App ID, private key (PEM formatted), and installation ID.
  APP_ID=
  PRIVATE_KEY=
  INSTALLATION_ID=
  

---

2. File: .gitignore

Lines: 1-5, 140

• Issue: Redundant entries exist for .env files between lines 1-5 and within the added block (e.g., .env, .env.local, .env.*).
• Change Request: Consolidate .env related entries to avoid redundancy. Example:

  # dotenv environment variable files
  .env*
  !.env.example
  

Line: 140

• Issue: .pnp.* is listed but lacks context. This may be too broad, as it could unintentionally ignore files that are necessary for specific development configurations.
• Change Request: Precisely specify the file patterns that should be ignored for pnp, if possible. For instance:

  # Yarn Plug'n'Play loader files
  .pnp.cjs
  .pnp.loader.mjs
  

---

Summary

The above issues should be addressed to improve clarity and avoid potential misconfigurations or redundancy.