You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the action finds any and all RDF files in the repository and validates their syntax. However when working on tools that process RDF it's quite common to include intentionally malformed files to test how bad inputs are handled. It would be nice if there was a way to explicitly exclude those files from being processed by this action.
The text was updated successfully, but these errors were encountered:
So as soon as I have a repository with one well formed RDF file and one intentionally malformed RDF file then the action will fail once triggered, regardless of whether I configure the workflow containing the action to only trigger when the well formed RDF file is modified
Currently the action finds any and all RDF files in the repository and validates their syntax. However when working on tools that process RDF it's quite common to include intentionally malformed files to test how bad inputs are handled. It would be nice if there was a way to explicitly exclude those files from being processed by this action.
The text was updated successfully, but these errors were encountered: