3
Option to toggle autosave and add version control for production code
Source: supabase/supabase#35146 · opened by @slooowshutter
Currently, the autosave feature presents a risk when working with production queries and functions. If we accidentally modify code and forget about it, changes are automatically saved and no way to get them back. Right now I pull my schema and commit it every now and then but it's not most reliable option.
Proposed solution:
• Add toggle option for autosave on specific saved snippets
• Implement version control to track changes
• Allow reverting to previous versions when mistakes occur
This would greatly improve safety when working with production code while maintaining the convenience of autosave for development work.
Proposed solution:
• Add toggle option for autosave on specific saved snippets
• Implement version control to track changes
• Allow reverting to previous versions when mistakes occur
This would greatly improve safety when working with production code while maintaining the convenience of autosave for development work.
No pledges yet. Be the first to back this.
Comments
Similar requests
Infrastructure as Code / config.toml for production
14 votes · 0 comments
Local supabase studio and supabase dashboard looks too similar.
3 votes · 0 comments
Supabase MCP Server for local development use
2 votes · 0 comments
Change color scheme on local database site so i can tell which tab is running locally
3 votes · 0 comments
Environment-Specific Database Schema Modifications
2 votes · 0 comments
No comments yet.