Norman Rusch

Hi @EricDunsworth, thank you for this detailed issue. This seems to be related to a unsupported encoding setting which is passed from editorconfig to [readFileSync](https://github.com/schorfES/node-lintspaces/blob/master/lib/Validator.js#L123). I think lintspaces needs to...

Hi @EricDunsworth, thank you for this detailed issue. You're totally right that lintspaces should react differently when getting the setting for newlines from .editorconfig (according the expected behaviour) or from...

Hi @EricDunsworth, thank you for this detailed issue. I think this is related to the [editorconfig-core-js](https://github.com/editorconfig/editorconfig-core-js) implementation itself. Without currently testing the response of editorconfig, I expect to receive the...

I have the same/similar issue. In my case it seems to be related to redirects that I am using. For example a `next/link` refers to a page at `/foo` but...

+1

Same here, receiving the following error when deleting an environment: ``` unexpected error encountered: HttpError: Resource not accessible by integration Error: unexpected error encountered: HttpError: Resource not accessible by integration...

> @schorfES Maybe, but I just realized that for our workflows I _thought_ we were using a PAT token, but we in fact were not, so that can cause problems...

Hi, even though we updated to the latest version 7.0.2, we are still facing this issue. Installed deps: ``` my-app └─┬ @release-it/[email protected] └── [email protected] ``` Error: ``` ERROR The "angular"...

Yes, we did. We are using yaml, but tried both yaml and json with the `name` prop you've mentioned.

Thank you @silversonicaxel, this is exactly the issue.