← Back to parent Epic
MAZENG-FT-39 · Publish generated project files through a branch and pull request
Why it matters
A team needs generated project files to enter Git through a reviewable change rather than becoming authoritative immediately.
Expected outcome
An attributable branch, commit, and pull request provide a normal review trail while leaving merge as a separate decision.
In scope
- Create or reuse the target repository without destroying existing content.
- Commit generated files to a named branch with attributable metadata.
- Open a pull request to the configured default branch and report durable links.
- Delivery status
IN_BACKLOG- Owner
- RootAtSkic
- Solution approval
- PENDING
Acceptance
Acceptance outcomes
- 01
Maze creates or reuses the project repository without destroying existing content.
- 02
Generated files are committed to a named branch with an attributable commit message.
- 03
A pull request targets the repository’s configured default branch.
- 04
The user receives the branch, commit, and pull-request links.
- 05
Merge remains a separate authorized review decision.
Dependencies and risks
Dependencies
None recorded.
Risks
- Publication depends on generated files and repository write and pull-request permissions.
- Legacy behavior automatically merges the pull request and must not be preserved.
- Legacy behavior assumes main and fixed or fallback GitHub App ownership.
- The API Git controller shell is empty while active routes live in a separate third-party module.
Authoritative Architecture tasks
No authoritative Architecture tasks are linked.