Prod 173 neon pass faq #53
Annotations
7 errors and 10 warnings
runner / vale:
README.md#L107
[vale] reported by reviewdog 🐶
[proselint-adapted.Annotations] 'TODO' left in text.
Raw Output:
{"message": "[proselint-adapted.Annotations] 'TODO' left in text.", "location": {"path": "README.md", "range": {"start": {"line": 107, "column": 4}}}, "severity": "ERROR"}
|
runner / vale
reviewdog: Too many results (annotations) in diff.
You may miss some annotations due to GitHub limitation for annotation created by logging command.
Please check GitHub Actions log console to see all results.
Limitation:
- 10 warning annotations and 10 error annotations per step
- 50 annotations per job (sum of annotations from all the steps)
- 50 annotations per run (separate from the job annotations, these annotations aren't created by users)
Source: https://github.community/t5/GitHub-Actions/Maximum-number-of-annotations-that-can-be-created-using-GitHub/m-p/39085
|
runner / vale:
docs/faq/fees.md#L42
[vale] reported by reviewdog 🐶
[Google-adapted.EmDash] Don't put a space before or after a dash.
Raw Output:
{"message": "[Google-adapted.EmDash] Don't put a space before or after a dash.", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 42, "column": 289}}}, "severity": "ERROR"}
|
runner / vale:
docs/token_transferring/neonpass_usage.md#L10
[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'NeonPass' instead of 'neonpass'.
Raw Output:
{"message": "[Vale.Terms] Use 'NeonPass' instead of 'neonpass'.", "location": {"path": "docs/token_transferring/neonpass_usage.md", "range": {"start": {"line": 10, "column": 49}}}, "severity": "ERROR"}
|
runner / vale:
docs/token_transferring/neonpass_usage.md#L11
[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'NeonPass' instead of 'neonpass'.
Raw Output:
{"message": "[Vale.Terms] Use 'NeonPass' instead of 'neonpass'.", "location": {"path": "docs/token_transferring/neonpass_usage.md", "range": {"start": {"line": 11, "column": 49}}}, "severity": "ERROR"}
|
runner / vale:
docs/tokens/token-accounts.md#L9
[vale] reported by reviewdog 🐶
[Vale.Terms] Use 'NeonPass' instead of 'neonpass'.
Raw Output:
{"message": "[Vale.Terms] Use 'NeonPass' instead of 'neonpass'.", "location": {"path": "docs/tokens/token-accounts.md", "range": {"start": {"line": 9, "column": 49}}}, "severity": "ERROR"}
|
runner / vale
reviewdog exited with status code: 1
|
runner / vale:
README.md#L107
[vale] reported by reviewdog 🐶
[write-good-adapted.todo] 'TODO' left in text
Raw Output:
{"message": "[write-good-adapted.todo] 'TODO' left in text", "location": {"path": "README.md", "range": {"start": {"line": 107, "column": 4}}}, "severity": "WARNING"}
|
runner / vale:
docs/faq/fees.md#L16
[vale] reported by reviewdog 🐶
[Google-adapted.Passive] In general, use active voice instead of passive voice ('are paid').
Raw Output:
{"message": "[Google-adapted.Passive] In general, use active voice instead of passive voice ('are paid').", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 16, "column": 25}}}, "severity": "INFO"}
|
runner / vale:
docs/faq/fees.md#L39
[vale] reported by reviewdog 🐶
[Google-adapted.Abbreviations] Spell out 'EIP', if it's unfamiliar to the audience.
Raw Output:
{"message": "[Google-adapted.Abbreviations] Spell out 'EIP', if it's unfamiliar to the audience.", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 39, "column": 49}}}, "severity": "INFO"}
|
runner / vale:
docs/faq/fees.md#L39
[vale] reported by reviewdog 🐶
[Google-adapted.Passive] In general, use active voice instead of passive voice ('is burned').
Raw Output:
{"message": "[Google-adapted.Passive] In general, use active voice instead of passive voice ('is burned').", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 39, "column": 72}}}, "severity": "INFO"}
|
runner / vale:
docs/faq/fees.md#L39
[vale] reported by reviewdog 🐶
[write-good-adapted.exchange] Consider using 'but (or nothing)' instead of 'however'. This makes it simpler and clearer.
Raw Output:
{"message": "[write-good-adapted.exchange] Consider using 'but (or nothing)' instead of 'however'. This makes it simpler and clearer.", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 39, "column": 83}}}, "severity": "WARNING"}
|
runner / vale:
docs/faq/fees.md#L39
[vale] reported by reviewdog 🐶
[write-good-adapted.TooWordy] 'however' can you drop this word/phrase?.
Raw Output:
{"message": "[write-good-adapted.TooWordy] 'however' can you drop this word/phrase?.", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 39, "column": 83}}}, "severity": "WARNING"}
|
runner / vale:
docs/faq/fees.md#L42
[vale] reported by reviewdog 🐶
[Google-adapted.Passive] In general, use active voice instead of passive voice ('is burned').
Raw Output:
{"message": "[Google-adapted.Passive] In general, use active voice instead of passive voice ('is burned').", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 42, "column": 125}}}, "severity": "INFO"}
|
runner / vale:
docs/faq/fees.md#L42
[vale] reported by reviewdog 🐶
[write-good-adapted.E-Prime] Try to avoid using 'being'.
Raw Output:
{"message": "[write-good-adapted.E-Prime] Try to avoid using 'being'.", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 42, "column": 275}}}, "severity": "INFO"}
|
runner / vale:
docs/faq/fees.md#L42
[vale] reported by reviewdog 🐶
[Google-adapted.Passive] In general, use active voice instead of passive voice ('being exceeded').
Raw Output:
{"message": "[Google-adapted.Passive] In general, use active voice instead of passive voice ('being exceeded').", "location": {"path": "docs/faq/fees.md", "range": {"start": {"line": 42, "column": 275}}}, "severity": "INFO"}
|
runner / vale:
docs/faq/neonpass.md#L14
[vale] reported by reviewdog 🐶
[Google-adapted.FirstPerson] Avoid first-person pronouns such as ' I '.
Raw Output:
{"message": "[Google-adapted.FirstPerson] Avoid first-person pronouns such as ' I '.", "location": {"path": "docs/faq/neonpass.md", "range": {"start": {"line": 14, "column": 11}}}, "severity": "WARNING"}
|