We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
i created the following autotag definition
dirs = [{"name":["*tmp*","*TMP*","*temp*","*TEMP*","*Temp*","*cache*","*CACHE*","*Cache*","*to*delete*"],"name_exclude":["*emperatur*","*emplate*"],"path":[],"path_exclude":[],"mtime":90,"atime":0,"ctime":90,"tag":"delete","tag_custom":"autotag"},{"name":["*FORMER*LAB*MEMBERS*"],"name_exclude":[],"path":[],"path_exclude":[],"mtime":0,"atime":0,"ctime":0,"tag":"archive","tag_custom":"autotag"}]
but the autotagger only tags the first definition
The text was updated successfully, but these errors were encountered:
So directories with *FORMER*LAB*MEMBERS* in their names are not getting tagged at all?
*FORMER*LAB*MEMBERS*
Sorry, something went wrong.
can you reply with an example full path directory that is not getting tagged? Are you restarting the bots after editing the diskover.cfg tags ?
currently autotag does not support wildcard character * in middle of name or path. Wildcard can only be at beginning, end or beginning and end.
ahhhh... the folder is called 'FORMER LABMEMBERS' no wonder its not getting tagged
No branches or pull requests
i created the following autotag definition
dirs = [{"name":["*tmp*","*TMP*","*temp*","*TEMP*","*Temp*","*cache*","*CACHE*","*Cache*","*to*delete*"],"name_exclude":["*emperatur*","*emplate*"],"path":[],"path_exclude":[],"mtime":90,"atime":0,"ctime":90,"tag":"delete","tag_custom":"autotag"},{"name":["*FORMER*LAB*MEMBERS*"],"name_exclude":[],"path":[],"path_exclude":[],"mtime":0,"atime":0,"ctime":0,"tag":"archive","tag_custom":"autotag"}]
but the autotagger only tags the first definition
The text was updated successfully, but these errors were encountered: