Discussion for #115 "subscribe" to issues implementation.
Users should be able to subscribe to issue, PR, or specific repo with event filtering. For example they should be able to subscribe to specific issue's state change instead of all comments under it. They should be able to "watch" the repository for new PRs but not including issues.
So... "follow user", "subscribe issue/pr", "watch repo" all seems quite similar behavior. Using same lexicon for all 3 connection seems quite doable.
- Should we use same lexicon for all these connections?
- Should we use dedicated lexicons? if so, should "subscribing issue" and "watching repo" be different lexicons?
I think "follow" could be used as a lexicon.
you can:
this would reduce the cognitive overhead imo, and is already quite similar to how social media works currently