반복 이벤트에 개별 이벤트 주제 만들기

Ethsim2 · 9월 3, 2026, 12:02오후

여기서 일부 진전이 있었습니다.

워크플로우용 Event ended 트리거가 이제 병합되었습니다:

github.com/discourse/discourse

FEATURE: Workflow triggers for event participation and event end (#42634)

main ← events-workflow-triggers

merged 10:09AM - 02 Sep 26 UTC

ZogStriP

+877 -72

Previously, the events plugin had no way to drive a workflow from an RSVP or fro…m an event finishing, and a trigger node contributed by any plugin was added to the registry but never subscribed to its `DiscourseEvent` — so it saved fine, showed up in the palette, and silently never fired. This change wires the subscription into node registration, which drops the hand-rolled `on(...)` workarounds in assign, topic voting and chat, and adds `trigger:event_participation_changed` and `trigger:event_ended`, both scopable to a single topic. --- Split into two commits, since the first touches shared infrastructure: - **`FIX: Subscribe trigger events for workflow nodes added by plugins`** — claiming a node now registers *and* subscribes it, and contributing plugins are flushed before the host claims its own, so ownership lands on them. Because the subscription goes through `Plugin::Instance#on`, a node stops listening while *its own* plugin is disabled rather than following the host's setting. This also drops a duplicate registration that let `trigger:chat_message_created` show in the palette while chat was disabled. - **`FEATURE: Workflow triggers for event participation and event end`** — the two triggers. No `on(...)` wiring needed in the events plugin thanks to the commit above. Three behaviour changes in the events plugin, each deliberate: - Withdrawing an RSVP destroyed the record without publishing anything, so attendance state built from these triggers could never recover from someone leaving. Removal now publishes, and reads as `status: null` with `removed: true`. The livestream chat sync skips removals, so its follow/unfollow behaviour is unchanged. - The ended occurrence travels with `:discourse_post_event_event_ended`. `set_next_date` moves the event on immediately afterwards, and `Event#starts_at` returns `nil` once a bounded series is past `recurrence_until`, so the event alone cannot say which occurrence ended. - Re-submitting an unchanged RSVP still publishes, so the trigger ignores it rather than running a workflow twice for one decision. Payload is `{event, post, topic, stats}`, plus `{user, participation}` on the participation trigger — modelled on `WebHook.build_calendar_event_payload` rather than `EventSerializer`, which goes admin-truthy under a system guardian. No JS, no core changes, no new site settings. ### Known gaps, documented rather than fixed Bulk invite, `Event#create_invitees` (`insert_all!`), `reset_invitee_notifications` (`update_all`), `enforce_private_invitees!` (`delete_all`) and event/user destroy stay silent. `create_attendance!` swallows `RecordNotUnique`, so a concurrent first RSVP fires nothing. `event_ended` can re-fire if an edit resets `finished_at`, and is missed when an event is closed early: `EventDate.pending` merges `Event.open`, so the in-flight occurrence leaves the job's scope. `EventListener` does not rescue `new`/`valid?`/`matches?` and `DiscourseEvent.trigger` re-raises, so a raising subscriber aborts `MonitorEventDates` mid-`find_each`. Adding `continue_on_error:` there breaks existing `track_events` assertions, so it is left for its own commit. ### Testing Full `discourse-workflows` and `discourse-events` backend suites pass (4005 examples), plus the workflow specs in chat, assign and topic voting. Verified at runtime that all 22 trigger nodes have exactly one subscription and there are no duplicate registrations, and that both new nodes disappear from the palette and stop dispatching when `discourse_events_enabled` is off. Meta: https://meta.discourse.org/t/discourse-calendar-events-webhook-triggers-automations-plugin/409623

또한 워크플로우에는 이미 기존 주제를 Get하고 새 주제를 Create할 수 있는 Topic 액션이 있으며, Wait 노드도 있습니다. 따라서 제안된 롤오버의 상당 부분은 전용 이벤트별 아카이빙 기능이 아니라 워크플로우로 구성할 수 있을 가능성이 큽니다.

다음과 같은 구조가 가능합니다:

Event ended → Wait → Topic / Get → Topic / Create

이 방식을 사용하면 기존 주제의 제목/본문/카테고리 데이터를 사용하여 후속 주제를 생성하는 동시에, 완료된 주제는 그대로 아카이브로 유지할 수 있습니다.

아직 확인이 필요한 부분은 기존 주제의 어떤 부분을 자동으로 복사할 것인지입니다. 예를 들어 태그, 업로드 파일, 이벤트 반복 상태, 그리고 답글을 이동할지 아니면 그대로 둘지 여부 등이 해당됩니다.

저는 또한 워크플로우에 Event 액션을 도입하는 오픈된 PR이 있습니다:

github.com/discourse/discourse

FEATURE: Add event actions to workflows (#42932)

main ← Ethsim12:workflow-event-close

opened 06:39PM - 26 Aug 26 UTC

Ethsim12

+546 -0

## What does this change? Adds an `Event` action to Discourse Workflows, allo…wing a workflow to: - Close an event - Open an event The action accepts a topic ID and optional actor. The event is resolved from the topic's first post, consistent with the Events plugin's existing requirement that an event belongs to the first post. Rather than updating the event record directly, the action updates the `[event]` block in the post raw using the normal workflow post-editing path. This allows the existing Events post-edit synchronization to update the persisted event state. Edits use the workflow execution context's `edit_post`, which applies the actor's normal post-edit permissions and uses `skip_workflows: true` to avoid recursively triggering workflows from the event state change. The action is idempotent when the event is already in the requested state. ## Example A `Post created` trigger can use: - Action: `Event` → `Close event` - Topic ID: `Input → topic.id` - Performed by user: System user This allows, for example, a reply to an event topic to automatically close the event without closing the topic itself. ## Testing - RuboCop: no offenses - Syntax Tree: all files match expected format - New Event workflow specs after final rebase: 8 examples, 0 failures - Full `discourse-events` suite before final formatting/rebase: 1124 examples, 0 failures - Manual browser test confirmed: - `Post created` → `Event / Close event` - dynamic `topic.id` - System user actor - replying to the topic immediately changed the event to `Closed` - the topic itself remained open - the change appeared live without a page refresh - workflow execution completed successfully ## Screenshots ### Event workflow actions <img width="1920" height="965" alt="workflow_screen_with_events_menu" src="https://github.com/user-attachments/assets/d283e9e6-e1db-4f5e-8cf9-3ed5c31f55fc" /> ### Configuring the Event action with the triggering topic <img width="1921" height="1003" alt="configuring_events_step" src="https://github.com/user-attachments/assets/725e28ca-f8f2-45f3-b124-4c3310c69eb9" /> ### Event automatically closed after the workflow runs <img width="1920" height="1000" alt="event_topic_after_auto_close" src="https://github.com/user-attachments/assets/a66138ad-bbaa-498a-9d87-2bd1eef9e495" />

기본 PR에는 Close event와 Open event가 포함되어 있으며, Set attendance를 추가하는 스택된 후속 PR도 있습니다:

github.com/discourse/discourse

FEATURE: Add event attendance workflow action (#43028)

main ← Ethsim12:workflow-event-attendance

drafted 01:21PM - 29 Aug 26 UTC

Ethsim12

+932 -0

Depends on #42932. This is a stacked follow-up to #42932 adding `Set attendance…` to the Event workflow action. Until #42932 merges, GitHub's diff also contains the prerequisite Event action changes. Once #42932 is merged, this branch will be rebased onto the updated `main` so this PR contains only the attendance changes.

해당 액션은 구조적으로, 적절한 경우 추가적인 이벤트 전용 작업을 별도의 후속 작업으로 추가할 수 있도록 설계되었습니다.

글		댓글	조회수
Discourse Events Plugin official , events , included-in-core	169	62617	9월 6, 2026
Angus' Events Plugin :calendar: Plugin	869	103918	7월 31, 2026
Calendar plugin features to make it really useful for us Feature events	8	3289	10월 6, 2022
Repeating Event " going" gets not deleted anymore Bug events , fixed	18	560	6월 12, 2026
Discourse Calendar updated to use fullcalendar 6 Announcements events	35	1784	2월 13, 2026

반복 이벤트에 개별 이벤트 주제 만들기

Related topics