// Set the allowed mentions filter which blocks all mentions from generating notifications.
response.setAllowedMentions(allowedMentions);
This was not always the default behavior for replies. Early in the operational history, the filter was not implemented and users would receive effectively random notifications whenever a reply contains a mention. Some users have expressed a preference to restore this behavior.
All replies are currently configured with an allowed mentions filter which suppresses any mentions from generating notifications (pings) to users.
https://git.logal.dev/LogalDeveloper/Crabstero/src/commit/89ee198897081e6f5a43e2e96e1f11dff266f160/src/main/java/dev/logal/crabstero/utils/MarkovChainMessages.java#L38-L43
https://git.logal.dev/LogalDeveloper/Crabstero/src/commit/89ee198897081e6f5a43e2e96e1f11dff266f160/src/main/java/dev/logal/crabstero/utils/MarkovChainMessages.java#L103-L104
This was not always the default behavior for replies. Early in the operational history, the filter was not implemented and users would receive effectively random notifications whenever a reply contains a mention. Some users have expressed a preference to restore this behavior.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
All replies are currently configured with an allowed mentions filter which suppresses any mentions from generating notifications (pings) to users.
This was not always the default behavior for replies. Early in the operational history, the filter was not implemented and users would receive effectively random notifications whenever a reply contains a mention. Some users have expressed a preference to restore this behavior.