Skip to content
Snippets Groups Projects

Add support for follow request notifications

Merged Eugenij requested to merge eugenijm/pleroma-fe:follow-request-notification into develop
3 unresolved threads

Closes #823 (closed) and #822 (closed)

Screenshot

follow-request-notification

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
6 6 ## [Unreleased]
7 7
8 8 ## [2.0.2] - 2020-04-08
9 ### Add
  • Maintainer

    I think we need to put this under ## [Unreleased-patch] section which doesn't exist yet in PleromaFE repo. (2.0.2 was already released.)

  • why do we need an [Unreleased-patch], if it's already under [Unreleased]? we're not picking and choosing changes for releases atm

  • I'm legit confused about this so would like some clarity, what purpose does the patch serve here? this doesn't seem like a change that needs to be treated differently to other currently unreleased stuff

  • Please register or sign in to reply
  • Eugenij added 1 commit

    added 1 commit

    • 299dc62b - Add support for follow request notifications

    Compare with previous version

  • Eugenij resolved all threads

    resolved all threads

  • Eugenij added 7 commits

    added 7 commits

    Compare with previous version

  • Shpuld Shpludson
  • Overall the code looks pretty good to me! I'll test it as well

  • Eugenij added 1 commit

    added 1 commit

    • 01b07f01 - Add support for follow request notifications

    Compare with previous version

  • Eugenij resolved all threads

    resolved all threads

  • Eugenij mentioned in merge request pleroma!2447 (merged)

    mentioned in merge request pleroma!2447 (merged)

  • mentioned in merge request pleroma!2451 (merged)

    • Once this MR is merged, we need to update PleromaFE bundle in BE MR making follow request notifications non-optional, as discussed previously: pleroma!2451 (merged).

    • Makes sense to me, I'm thinking about release arrangements but it'll probably be fine as it is. No need to mark a release on FE's changelog when BE develop bundles something, only when BE has a release

    • Please register or sign in to reply
  • mentioned in commit c67e9daf

  • mentioned in issue #823 (closed)

  • Please register or sign in to reply
    Loading