Skip to content

Add Event Props booking lifecycle fields - #188

Closed
z-mailme wants to merge 23 commits into
trycompai:mainfrom
z-mailme:codex/event-booking-statuses
Closed

Add Event Props booking lifecycle fields#188
z-mailme wants to merge 23 commits into
trycompai:mainfrom
z-mailme:codex/event-booking-statuses

Conversation

@z-mailme

@z-mailme z-mailme commented Aug 28, 2026

Copy link
Copy Markdown

Adds Event Props for Hire SA booking lifecycle support.

Includes:

  • Event Props deal-stage labels
  • Quote status
  • Invoice status
  • Payment status
  • Calendar status
  • Booking lifecycle timestamps
  • Google Calendar event ID
  • Deposit amount
  • Balance amount
  • REST API PATCH support
  • Deal booking-status UI section
  • Prisma migration: 20260828120000_event_booking_statuses

Source commit:
09eff59

Important:
Do not deploy or run the production database migration until the PR has been reviewed and merged.


Summary by cubic

Adds event booking lifecycle tracking to deals: quote, invoice, payment, and calendar statuses with timestamps, deposit/balance amounts, and a Google Calendar event ID.

  • Extends the deal update contract and service to persist the new fields; existing deals keep safe defaults.
  • Adds an "Event / booking status" section to the deal sheet showing each status, its timestamp, and deposit/balance amounts.
  • Renames deal stage labels to booking terms (Demo bookedNew Enquiry, Closed wonBooked, etc.).

Migration

  • Run 20260828120000_event_booking_statuses only after this PR is reviewed and merged; it adds columns with safe defaults.

Written for commit 09eff59. Summary will update on new commits.

Review in cubic

carhartlewis and others added 23 commits August 7, 2026 11:38
@vercel

vercel Bot commented Aug 28, 2026

Copy link
Copy Markdown

@z-mailme is attempting to deploy a commit to the Comp AI - PoC Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
github-actions Bot changed the base branch from release to main August 28, 2026 08:22
@github-actions

Copy link
Copy Markdown
Contributor

Retargeted this onto main.

release is the default branch so that a plain clone runs the last tagged release, but nothing merges into it — it is fast-forwarded onto the tag by the Release workflow and that is all. Changes go to main, and reach release when a release is cut.

Nothing is wrong with your branch. If the diff now shows commits that are already on main, rebase and force-push:

git fetch origin main
git rebase origin/main
git push --force-with-lease

@z-mailme z-mailme closed this Aug 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants