AnotherKamila / AnotherKamila/bsdops
Unconfuse the two repositories weirdness
- Lenguaje dominante
- Shell
- Estrellas
- 11
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Evaluación
Este issue todavía no se ha evaluado.