Page MenuHomePhabricator

[keyserver] remove commbot after creating community
AbandonedPublic

Authored by will on Oct 29 2024, 4:29 PM.
Tags
None
Referenced Files
F3382347: D13813.diff
Thu, Nov 28, 10:04 AM
Unknown Object (File)
Wed, Nov 13, 9:07 PM
Unknown Object (File)
Wed, Nov 6, 1:15 PM
Unknown Object (File)
Tue, Nov 5, 1:00 AM
Unknown Object (File)
Mon, Nov 4, 4:03 PM
Unknown Object (File)
Mon, Nov 4, 3:51 PM
Unknown Object (File)
Sat, Nov 2, 10:19 PM
Unknown Object (File)
Wed, Oct 30, 5:18 PM
Subscribers

Details

Reviewers
varun
ashoat
Summary

This removes commbot after it creates the community. There will always be another keysrver admin as it will either be the tagger, channel lead, or the keyserver admin.

Depends on D13775

Test Plan

Tested by auto-creating a community for the dgn channel and confirming that after commbot had created the community, the tagger userID was promoted to admin and commbot did not appear on members.

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

will requested review of this revision.Oct 29 2024, 4:50 PM
ashoat requested changes to this revision.Oct 29 2024, 7:08 PM

See feedback in D13812 – we wouldn't need to remove commbot if we never add them to the thread

This revision now requires changes to proceed.Oct 29 2024, 7:08 PM

Abandoning this diff. We're going with the approach introduced in https://phab.comm.dev/D13819 where commbot is added as a ghost