I fully support the suggestion for integrating Rewst with GitHub or a similar version control system. This capability would significantly enhance the management of our workflows, forms, and other elements by allowing us to track changes systematically and revert to previous versions when necessary.

In the absence of a direct integration with GitHub, an alternative that would also meet our needs involves the automated export of JSON files documenting the detailed changes. These files could then be organized on a SharePoint site within designated subfolders for each category (e.g., workflows, forms), and further subdivided by specific item names. Each change would be recorded in a file named according to the date of modification, following a structured format like: RewstBackups\Workflows\[WorkflowName]\YYYY-MM-DD.json.

While GitHub integration might provide the most robust solution for version control, the SharePoint-based export option could serve as an effective interim measure. Currently, our ability to preserve a history of changes is limited to manually creating backups from the detailed change log each time an item is saved, which is both cumbersome and prone to error.

Introducing either of these features would be immensely beneficial for our organization, ensuring better governance and greater efficiency in managing changes within Rewst.

If I may be frank, it is quite perplexing that a platform as advanced as Rewst was launched without integrated version control. The absence of this fundamental feature from the outset compromises our ability to effectively manage complex systems, setting us up for potential failures rather than success. We firmly believe that addressing this oversight should be a top priority for Rewst.

I love this idea, especially with multiple rewsters in our kewp

Yes please!

and auto-save!