abcxyz / abcxyz/abc

Support templates affecting multiple destination repos

未關閉
#23 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
enhancement needs design doc
主要語言
Go
星號
16
分支
4
PR 合併指標
30 天內沒有已合併 PR

描述

### TL;DR

Some templates will want to touch multiple repositories to create a single service. For example, we might drop the service source code in one repo, and drop terraform files in a separate repo. Maybe we want to make this a single command to keep things simple for users. Our current solution would be just to ask the user to install two separate templates in different repos.

This task includes both designing and implementing such a thing.

### Detailed design

_No response_

### Alternatives considered

_No response_

### Additional information

_No response_

貢獻指南

開啟貢獻指南

研究方向

The issue describes a design and implementation task for a template system that can affect multiple repositories. Start by examining the existing template command and repository structure in the codebase. Look for where templates are defined and applied. Understanding the current single-repo template flow is necessary before extending it to multi-repo support.

由索引模型根據 Issue 內容生成。

評估

技術堆疊
go
領域
cli, tooling
Issue 類型
功能
難度
5/5
預估耗時
一週以上
活躍度
停滯
描述清晰度
需要釐清
新手友好度
20/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。