chore(repo): remove depraceted env file usages

[Brazol]

Summary by CodeRabbit

• Documentation

  • Simplified setup instructions by removing environment file configuration steps.

• Chores

  • Streamlined build workflows by removing environment variable management.
  • Consolidated sample user configuration into hardcoded values for easier onboarding.

[coderabbitai]

Walkthrough

The pull request removes environment-based configuration for sample users across the project. It eliminates ENV_PROPERTIES from CI/CD workflows, deletes sample user credentials from env.sample, replaces dynamically-loaded user data with hard-coded values in the example app, removes the Env configuration class, and updates setup documentation.

Changes

Cohort / File(s)	Summary
CI/CD Workflow Updates .github/workflows/app-distribute.yml, .github/workflows/stream_video_flutter_workflow.yml	Removed ENV_PROPERTIES environment variable from workflow global env and eliminated steps that echoed ENV_PROPERTIES into .env files before running melos commands in build and analyze jobs.
Documentation README.md	Removed env-file creation and templating steps from the "Process to get started" section and simplified melos generate:all instructions.
Environment Configuration env.sample	Deleted DOGFOODING_API_KEY, SAMPLE_STREAM_VIDEO_API_KEY, SAMPLE_STREAM_CHAT_API_KEY, and all SAMPLE_USER entries (IDs, names, roles, images, tokens) for six sample users.
Example App Configuration packages/stream_video_flutter/example/lib/app_config.dart	Replaced Env-based sample user data references with hard-coded UserInfo entries containing explicit id, name, role, and image values with avatar URLs.
Env Abstraction Layer packages/stream_video_flutter/example/lib/env/env.dart	Removed entire Env configuration class with @envied annotation, generated accessors, and all static const fields for six sample users (sampleUserId00 through sampleUserImage05). Deleted envied package imports and part directive.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 A rabbit hops through configs once bound to the .env,
Hard-coding paths where env vars would dwell—
No more secrets dancing in workflow files,
Sample users now carved in stone with a smile!
The Env class bids farewell, our code runs so well.

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	The pull request description is entirely absent. The template specifies required sections including Goal, Implementation details, Testing, and both Contributor and Reviewer checklists, none of which have been provided. This represents a significant gap as the description should explain why the deprecated env file usages are being removed, how the implementation replaces those patterns, and how the changes can be validated. Without this context, reviewers lack essential information for understanding the intent and implications of the changeset.	The author should add a comprehensive pull request description following the repository template. At minimum, include the Goal section explaining why deprecated env files are being removed, Implementation details describing how the transition to hardcoded user data was accomplished, Testing section explaining how the changes were validated, and completion of the Contributor Checklist to ensure proper review and documentation procedures are followed.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The pull request title "chore(repo): remove depraceted env file usages" accurately describes the main changes in the changeset. The modifications across multiple files consistently focus on removing deprecated environment file usage patterns: ENV_PROPERTIES is removed from workflows, the .env creation steps are eliminated, env.sample is trimmed of configuration entries, the Env class is deleted, and hardcoded user data replaces environment variable references. The title is specific enough to convey the primary purpose of the changeset and aligns with the actual changes implemented.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/remove-deprecated-env-requiremnet

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 09cfc71 and 0385a96.

📒 Files selected for processing (6)

• .github/workflows/app-distribute.yml (0 hunks)
• .github/workflows/stream_video_flutter_workflow.yml (0 hunks)
• README.md (1 hunks)
• env.sample (0 hunks)
• packages/stream_video_flutter/example/lib/app_config.dart (1 hunks)
• packages/stream_video_flutter/example/lib/env/env.dart (0 hunks)

💤 Files with no reviewable changes (4)

• .github/workflows/stream_video_flutter_workflow.yml
• packages/stream_video_flutter/example/lib/env/env.dart
• env.sample
• .github/workflows/app-distribute.yml

🧰 Additional context used

🪛 LanguageTool

README.md

[style] ~42-~42: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ...fetch dependencies for all projects. 6. Run melos generate:all to generate the re...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: stream_video_screen_sharing
• GitHub Check: stream_video
• GitHub Check: stream_video_noise_cancellation
• GitHub Check: stream_video_push_notification
• GitHub Check: stream_video_flutter
• GitHub Check: build
• GitHub Check: analyze

🔇 Additional comments (2)

README.md (1)

42-42: LGTM! Documentation correctly reflects the simplified setup process.

The removal of env file setup steps and simplification of the melos generate command description aligns well with the broader removal of environment-based configuration.

packages/stream_video_flutter/example/lib/app_config.dart (1)

3-56: LGTM! Migration from env-based to hard-coded configuration is complete.

The verification confirms no remaining imports of env.dart or references to the Env class in the codebase. The hard-coded user data in app_config.dart is properly structured with const constructors appropriate for this immutable configuration.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 4.83%. Comparing base (c8683bf) to head (f64cda9).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@          Coverage Diff          @@
##            main   #1087   +/-   ##
=====================================
  Coverage   4.83%   4.83%           
=====================================
  Files        591     591           
  Lines      40508   40508           
=====================================
  Hits        1960    1960           
  Misses     38548   38548           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.