chore(backend) : add ts-backend-check config and CI workflow

[MuraliChowdhary]

Contributor Checklist

• This pull request is on a separate branch and not the main branch
• I have run the backend and frontend tests depending on what's needed for my changes as described in the testing section of the contributing guide

Description

This PR integrates the ts-backend-check CLI into the Activist backend CI to ensure consistency between Django backend models and the corresponding TypeScript types used in the frontend.

Configuration

Adds a .ts-backend-check.yaml configuration file at the repository root that defines checks for the following model ↔ type mappings:

• backend/communities/organizations/models.py ↔ frontend/shared/types/organization.d.ts (organizations)
• backend/communities/groups/models.py ↔ frontend/shared/types/group.d.ts (groups)
• backend/events/models.py ↔ frontend/shared/types/event.d.ts (events, mapped to the CommunityEvent interface)

CI Workflow

Introduces a dedicated GitHub Actions workflow:

pr_ci_ts_backend_check

Workflow steps:

uv sync --frozen --all-extras 

uv run --project ./backend ts-backend-check -a 

Workflow Triggers

Runs on PRs and pushes that modify:

backend/**/models.py frontend/shared/types/**/*.{ts,d.ts} 

Current Status

• The workflow and configuration are wired up and working
• ts-backend-check runs successfully in CI
• Currently reports mismatches between Django models and TypeScript types for:

• organizations
• groups
• events

These differences can be addressed in this PR or in follow-up changes depending on reviewer preference.

Testing

Backend

Run from backend/:

uv sync --all-extras uv run pytest . 

Type Checks

Run from the repository root:

uv run --project ./backend ts-backend-check -a 

Verified that the command runs using the new YAML configuration and reports the current set of model / type mismatches for organizations, groups, and events.

Related Issue

Closes #1325

[netlify]

✅ Deploy Preview for activist-org ready!

Name	Link
🔨 Latest commit	74ba564
🔍 Latest deploy log	https://app.netlify.com/projects/activist-org/deploys/69b29a986b54cb000899a3b4
😎 Deploy Preview	https://deploy-preview-2000--activist-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

Thank you for the pull request! ❤️

The activist team will do our best to address your contribution as soon as we can. The following are some important points:

• Those interested in developing their skills and expanding their role in the community should read the mentorship and growth section of the contribution guide
• If you're not already a member of our public Matrix community, please consider joining!
  • We'd suggest that you use the Element client as well as Element X for a mobile app
  • Join the General and Development rooms once you're in
• Also consider attending our bi-weekly Saturday developer syncs!
  • Details are shared in the Development room on Matrix each Wednesday before the sync
  • It would be great to meet you 😊

Note

activist uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the TypeScript, pytest and formatting workflows within the PR checks do not indicate new errors in the files changed

• The Playwright end to end and Zap penetration tests have been ran and are passing (if necessary)

• The changelog has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[github-actions]

First PR Commit Check

• The commit messages for the remote branch of a new contributor should be checked to make sure their email is set up correctly so that they receive credit for their contribution
  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local activist repo (can be set with git config --global user.email "GITHUB_EMAIL")