-
Notifications
You must be signed in to change notification settings - Fork 0
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
Ignore Icon? #66
Comments
Interesting, that's a new one for me I haven't seen Integrity should already exclude and ignore the sans-integrity.yml, but if it isn't that seems to be a regression. |
@joswr1ght integrity has an additional ignore feature, you can pass It adds to the Always Ignore list which is the |
In re-reading after a slack conversation, I meant to be way more specific. First we can easily add more files to the ignore list, including Second, to test adding any files for exclusion you can always add by using the If you can confirm if you are seeing issues with sans-integrity.yml not being excluded, I might need some more details as we haven't changed anything in a while and it was originally excluded. There could be some regression happening. |
macOS 13.3 on x64:
The file is called
Using Integrity with
It's possible this file is introduced by having an extra icon in my Finder (which I used with Applescript to open an iTerm in the current directory displayed by Finder), as shown here, though I've had that icon for a long time and I don't remember having to take extra steps with Integrity to ignore this I think this file name is a candidate for addition to |
My Integrity files often fail validation during courseware processing because macOS insists on making an Icon? (
Icon\r
) file. macOS doesn't allow me to delete this file from my lab files directory, so I need to manually edit the YAML file to remove the entry after creating the integrity file.Feature Request: Integrity should ignore this file and not calculate a checksum, nor should it include the file in the
sans-integrity.yml
file.The text was updated successfully, but these errors were encountered: