Skip to content

Conversation

@tchapi
Copy link
Owner

@tchapi tchapi commented Jan 31, 2026

Important

This PR contains a migration, that you need to run to be able to test the code. The migration is backwards compatible (meaning that running it adds a column, that is ignored if you rollback on an earlier version of the code)

@tchapi tchapi self-assigned this Jan 31, 2026
@tchapi tchapi force-pushed the tchapi/fix-public-calendars branch from a555baa to 7f42840 Compare February 1, 2026 13:14
@tchapi tchapi added bug Something isn't working enhancement New feature or request labels Feb 1, 2026
@tchapi tchapi force-pushed the tchapi/fix-public-calendars branch from 3a0895f to 831d7fb Compare February 1, 2026 14:07
@tchapi tchapi force-pushed the tchapi/fix-public-calendars branch from 831d7fb to 610a8a5 Compare February 1, 2026 16:19
@tchapi tchapi linked an issue Feb 1, 2026 that may be closed by this pull request
@tchapi tchapi changed the title [Chore] Change public behavior [Chore] Fix public calendar behavior Feb 1, 2026
@tchapi tchapi moved this to In Review in Davis Roadmap Feb 1, 2026
@tchapi
Copy link
Owner Author

tchapi commented Feb 1, 2026

Linked to Davis Roadmap too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

are public calendars always read only?

2 participants