Exclude example is badly formatted
See original GitHub issueThe example of “exclude” flag is not properly formatted for yaml and doesn’t run.
Additionally once all line are created the following format (guessing this was the intended format), it is not expected by the exclude flag
exclude:
- '.git*'
- '.git*/**'
- '**/.git*/**'
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Server Utilities » Exclude badly formatted - OraFAQ Forum
Im trying to use IMPDP, this is my EXCLUDE: Code: [Select all] [Show/ hide]. Exclude=INDEX,STATISTICS,SCHEMA:\"IN \(\'AWTEST\',\'AWPROD\' ...
Read more >How to Resolve ORA-39071: Value for EXCLUDE is badly ...
ORA-39071 means that the value you passed into the parameter is not well-formed and unrecognized, you should check the format of parameter.
Read more >how to fix badly formatted Dataframe - Stack Overflow
You need to drop a column with entire name. import pandas as pd import numpy as np import matplotlib.pyplot as plt from ...
Read more >Add ability to exclude files · Issue #864 · dart-lang/dart_style
I'm using dartfmt via flutter format, which I run it like this: flutter format . This formats all .dart files recursively, which is...
Read more >EXCLUDE - Oracle Help Center
It must be separated from the object type with a colon and enclosed in double quotation marks, because single quotation marks are required...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It looks like GitHub has changed some things, at the time tests were passing. I’ll take a look.
@SamKirkland - apologies, but the examples in the readme still seem to suffer from the same problem. They give a YAML list instead of a string, and GitHub rejects them as shown in the screenshot above. This is true as of the v4.1.0 release.