AnotherKamila / AnotherKamila/bsdops

Unconfuse the two repositories weirdness

未关闭
#11 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Shell
星标
11
派生
1
PR 合并指标
30 天内没有已合并 PR

描述

I started out with two repositories:

1. my fork of debops/debops: lives at anotherkamila/debops
2. this repository

This seemed like a good idea at the time, because I wanted the debops fork to be as close to upstream as possible, so I wanted a separate repository for evil hacks and documentation. This is currently a valid use case, as my `ansible/group_vars/freebsd/bsdops_required.yml` is an evil hack and can't really live inside the `debops` fork.

However, **after I close #1**, I should think about maybe making the `anotherkamila/debops` repository the "important" repository and changing this into a "less important" `bsdops-example` repository. I believe that it will be less confusing that way.

Doing that would involve the following:
- [ ] rename this to `bsdops-example`
- [ ] rename `anotherkamila/debops` to `anotherkamila/bsdops`
- [ ] put this repo's README into `anotherkamila/bsdops` (the important one), with the required modifications
- [ ] write a "this is an example BSDops project" README for this one

贡献指南

这个仓库没有索引到贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。