-
Notifications
You must be signed in to change notification settings - Fork 7
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
Notifications don't trigger for actions initiated by yourself #15
Comments
Can confirm with: |
Can confirm with: |
Cannot confirm on 20.0.8 / 1.0.3. Please note that the notification is not triggered, when you do the action yourself. |
Sorry, my mistake in testing after the update |
@blizzz Oh, so this is intended behavior? IMO, this could be configurable. I don't always access files manually, but also in various automated tasks via scripts, which might be a use case for this flow. Anyways, I'll test the app with another user and report back in a minute. |
Yes, it is intended and also worked like this. Does not mean it has to be like this forever (but then opt-in). |
Sorry, this was my fault! |
This should not be the case. There is no introspection into files. The check for ownership as pointed out above is the only one we do in this app. |
I have set up a simple test case:
The NC Talk flow is just there to verify that I didn't misconfigure the conditions. When I edit/rename a file called
test.md
totest1.md
(or vice versa), I get a message in Talk but no notification.NC version: 20.0.4
Flow Notifications version: 1.0.3
The text was updated successfully, but these errors were encountered: