forked from getredash/redash
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support version control for queries #7
Comments
Another interesting point brought up in bug 1315081 is, if we have a repo, one can put in a PR for a query. |
Backend support for this is in redash master now. All edits to queries and dashboards are saved to a |
|
Relevant: getredash#1550. |
Reopening bc there are JS errors preventing this from working correctly in production. |
washort
pushed a commit
that referenced
this issue
Mar 26, 2019
jezdez
pushed a commit
that referenced
this issue
May 13, 2019
jezdez
pushed a commit
that referenced
this issue
May 15, 2019
washort
pushed a commit
that referenced
this issue
Jun 10, 2019
jezdez
pushed a commit
that referenced
this issue
Jun 13, 2019
washort
pushed a commit
that referenced
this issue
Jun 27, 2019
washort
pushed a commit
that referenced
this issue
Jun 28, 2019
emtwo
pushed a commit
that referenced
this issue
Jul 15, 2019
emtwo
pushed a commit
that referenced
this issue
Jul 17, 2019
jezdez
pushed a commit
that referenced
this issue
Aug 12, 2019
jezdez
pushed a commit
that referenced
this issue
Aug 14, 2019
jezdez
pushed a commit
that referenced
this issue
Aug 19, 2019
washort
pushed a commit
that referenced
this issue
Sep 16, 2019
emtwo
pushed a commit
that referenced
this issue
Nov 5, 2019
jezdez
pushed a commit
that referenced
this issue
Jan 16, 2020
wlach
pushed a commit
to wlach/redash
that referenced
this issue
Jun 23, 2023
Update requirements_all_ds.txt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Users would like to be able to keep track of edits made to their queries, with the ability to see prior versions, to see diffs between versions, and to revert to earlier versions. Requiring an explicit action to save a version is acceptable. It seems reasonable to still use the database as the production source of the currently active query, rather than trying to load the query directly from whatever versioning mechanism is used.
The text was updated successfully, but these errors were encountered: