Skip to content

Pull requests: TIDES-transit/TIDES

New pull request New
11 Open 110 Closed
11 Open 110 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Reviews
Filter by reviews
No reviews Review required Approved review Changes requested
Assignee
Filter by who’s assigned
Assigned to nobody Loading
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Pull requests list

Add Governance > Roadmap page and placeholder Board action for TIDES Roadmap 2026-2027 📙 docs Elaborating or updating the documentation – inline or otherwise 🏛️ governance Pertains to the governance of the spec
#267 opened Jun 4, 2026 by chrisyamas Contributor • Draft
1
Add device_status table for tracking device availability 🔄 normative change A normative change requires approval of TIDES Board 📄 spec Pertains to the specification itself
#253 opened Jan 8, 2026 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
1
@chrisyamas
2
Rename passenger_events to device_events with expanded scope 🔄 normative change A normative change requires approval of TIDES Board 📄 spec Pertains to the specification itself
#251 opened Jan 8, 2026 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
@chrisyamas
7
Add new vehicle_label field to vehicles table 🚀 feature Adds a new feature - to spec or code 🔄 normative change A normative change requires approval of TIDES Board 📄 spec Pertains to the specification itself
#250 opened Dec 31, 2025 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
1
@chrisyamas
6
Rename duration fields with explicit suffix 🔄 normative change A normative change requires approval of TIDES Board 📄 spec Pertains to the specification itself
#249 opened Dec 30, 2025 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
@chrisyamas
6
Clarify event_count usage and APC data guidance 📙 docs Elaborating or updating the documentation – inline or otherwise 📝 non-normative Non-normative changes can be approved by other contributors 📄 spec Pertains to the specification itself
#248 opened Dec 30, 2025 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
1
@chrisyamas
1
Update event_type enum values to snake_case 📙 docs Elaborating or updating the documentation – inline or otherwise 🔄 normative change A normative change requires approval of TIDES Board 📄 spec Pertains to the specification itself
#247 opened Dec 30, 2025 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
1
@chrisyamas
4
Add vehicle_crew supporting table 🚀 feature Adds a new feature - to spec or code 🔄 normative change A normative change requires approval of TIDES Board restructuring For issues such as adding or removing tables, making significant chages to a table, etc. 📄 spec Pertains to the specification itself
#246 opened Dec 29, 2025 by chrisyamas Contributor Loading…
1 of 2 tasks
v2.0
1
@chrisyamas
8
add mermaid diagram with git graph diagram showing branching model
#214 opened Jan 13, 2024 by e-lo Contributor • Draft
1
@e-lo
2
Update issue templates to be consistent with governance. 🧹 chore
#212 opened Jan 13, 2024 by e-lo Contributor Loading…
1
@e-lo
2
Issue 40 validate example data
#75 opened Oct 7, 2022 by e-lo Contributor Loading…
@e-lo
83
ProTip! Type g i on any issue or pull request to go back to the issue listing page.