-
Notifications
You must be signed in to change notification settings - Fork 30
Link follow to notifications in article pages #15558
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
Open
aracho1
wants to merge
11
commits into
main
Choose a base branch
from
link-follow-to-notifications
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+112
−71
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
47418a6
link follow to notification state
aracho1 da7f128
remove notification opt out
aracho1 f10665d
css tweaks
aracho1 d77d093
auto enable notifications
aracho1 f3426d2
respect notification settings
aracho1 6e99ef4
update useEffect
aracho1 71747ce
move blocklist
aracho1 bbc206c
Merge branch 'main' into link-follow-to-notifications
aracho1 fc192bd
remove useState
aracho1 173218c
Merge branch 'main' into link-follow-to-notifications
aracho1 2b8b035
Merge branch 'main' into link-follow-to-notifications
aracho1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've assumed it's ok to create a new Sentry error type for this but please let me know if I should just use an existing one e.g. `'bridget-getTagClient-isFollowing-error'