scheduled event tracking #59
Open
opened 2024-05-17 11:00:16 -04:00 by imcompiling
·
1 comment
No Branch/Tag Specified
main
renovate/pytz-2026.x
renovate/ghcr.io-astral-sh-uv-0.x
renovate/python-3.x
renovate/pandas-3.x
renovate/setuptools-84.x
renovate/dataclass-wizard-1.x
renovate/actions-checkout-7.x
renovate/docker-login-action-4.x
renovate/aiofiles-25.x
81-sqlmodel
autoban-channel
test-some-util-functions
add-logging
update-python
82-uv
76-clan-points
no-election-bug-fix
78-config-for-skipping-election-cycle
77-verification-for-splits
21-edit-configs-from-discord
65-database-changes
74-Double-period-in-record-point-command
60-view-event-points-when-no-non-discord-members
71-catch-all-clan-participation
68-time-command
63-bad-sorting
52-update-packages
fix-ruff-lint-smells
64-Limit-weekly-event-points
49-view-votes-cant-see-HC-elections
61-Create-virtual-environment-and-update-python-version
54-Only-edit-changed-channels
55-Use-dakiny-messages-repo-for-message-templates
56-announce-clan-council
53-Not-recording-High-Council-results-in-CouncilMembers-database
6-add-clan-rules
51-event-participation-recording
44-sort-candidates
47-incorrect-election-cycle
42-q1-elections-wrong-name
40-remove-presence
39-view-presences
v1.1.0
36-bot-presence
35-remove-nomination-views
18-highcouncil-election
33-fixes-from-mock-election
30-threads
34-use-correct-sql-statement
mock-election
32-view-votes-command
28-add-election-reminder
11-council-member-vote-automation
29-update-name-of-channel
27-supporting-first-live-action
26-the-annoy-command
25-cakeday
22-daily-loop-not-starting-election
19-birthday-tracking
10-name-change-request
20-finish-daily-loop
15-term-start-action
14-high-council-election-action
13-voting-end-action
12-voting-start-action
3-sqlite-database
2-election-cycle-class
4-configuration-options
election-class-test
5-create-pipeline
1-daily-loop
v2.1.2
v2.1.1
v2.1.0
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v2.0.0
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.6.9
v1.6.8
v1.6.7
v1.6.6
v1.6.5
v1.6.4
v1.6.3
v1.6.2
v1.6.1
v1.6.0
v1.5.1
v1.5.0
v1.4.5
v1.4.4
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.3.0
v1.2.4
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.1.1
v1.0.1
v1.0.0
v0.2.1
v0.2.0
v0.1.1
v0.1.0
v0.0.6
v0.0.5
v0.0.4
v0.0.3
v0.0.2
v0.0.1
No labels
enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: imcompiling/dakiny-bot#59
Reference in New Issue
Block a user
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.
Kandy suggested tracking those who are interested in scheduled events. Then we can link those interested to the recorded event message to see who was interested and who showed up.
Need to refine exactly what is wanted.
I think I want to use the on scheduled event interest listener to add a user to the database, then when recording an event a scheduled event can be linked to. Everyone who is listed on the recorded event that was marked as interested in the scheduled event is then marked as attended, and I can have commands to view attendance rates of events and users.