π§ Centrally configure your decentralised π git repo.
Git, being an awesomely decentralised system, has ways to have decentralised configurations per user. However, times require certain configurations to be shared and tracked centrally among various collaborators. Some examples of centrally sharable configurations are:
- π» Branch descriptions (or better, branch READMEs).
- π‘Issues/Features/Tasks related to the repo.
- πͺΌ Certain properties that closely relate to the repo.
- π Rules related to per-branch collaborations and conventions.
- π Encrypted secrets.
- π Deployment, packaging and distribution mechanics.
- β¬οΈ ... and more
Repoconf is developed to address this issue. It stores central configuration in the __repoconf/default/main branch
and this centrally stored distributed configuration can be:
- π’ accessed using git config commands and aliases
- β added
- β removed
βοΈ pushedβοΈ pulled
... just like any other git branches ππ».
-
List all the configurations for the current repo
repoconf config --list
-
Add configuration
repoconf config branch.my-branch.description "This branch is created for something which one may not readily remember in the future." repoconf config branch.my-sharable-branch.description "This branch is to be shared with others and thus requires concise description on what it is created for."
... supports nearly all options that git config command supports.
See git config documentation for more details.
pip install repoconf