-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parse_env_file discard utf8 bom #2638
Conversation
* powershell 5 may add the BOM even when explicitly using utf8
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
@ChristopherHX this pull request has failed checks 🛠 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2638 +/- ##
==========================================
+ Coverage 61.56% 68.74% +7.18%
==========================================
Files 53 71 +18
Lines 9002 10956 +1954
==========================================
+ Hits 5542 7532 +1990
+ Misses 3020 2858 -162
- Partials 440 566 +126 ☔ View full report in Codecov by Sentry. |
@ChristopherHX this pull request has failed checks 🛠 |
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it. If you want to requeue this pull request, you need to post a comment with the text: |
@ChristopherHX this pull request has failed checks 🛠 |
powershell 5 may add the BOM even when explicitly using utf8
ask for confirmation in gitea discord