`MAZENG-EP-11` · Store, review, and version project files in Git

MAZENG-EP-11 · Epic

Delivery status: IN_BACKLOG
Status authority: EXACT
Owner: RootAtSkic (product lead)
Solution approval: PENDING

Goal

Maze can connect to GitHub and GitHub Enterprise to publish files, propose changes for review, keep named versions, and retrieve content from earlier releases.

Benefit

Project files can follow a familiar review and version-control process before teams use them.

Problem or opportunity

Teams need a recorded history and review path for the project files Maze generates.

Delivery scope

Features

MAZENG-FT-38IN_BACKLOG

Connect Maze to an authorized GitHub repository

A user needs to connect Maze to an approved GitHub repository without exposing raw access credentials to application code.

MAZENG-FT-39IN_BACKLOG

Publish generated project files through a branch and pull request

A team needs generated project files to enter Git through a reviewable change rather than becoming authoritative immediately.

MAZENG-FT-40IN_BACKLOG

Publish named semantic versions of a project

A team needs to mark meaningful project-file milestones with stable version identities and release notes.

MAZENG-FT-41IN_BACKLOG

View and restore an earlier project version

A user needs to inspect a historical project design safely and deliberately make it current again when necessary.

MAZENG-EP-11 · Store, review, and version project files in Git