At the beginning, the YAML contained only paths, then I needed labels, and I wanted to experiment, that's why I have them as
/path/to/the/repo [group-label][vanity-label]
This structure is ugly AF.
The end goal is to extract stats in terms of "I worked on those things", but:
- I want to create that summary and expose it on a website
- I want to have stats that differ from: personal/fun, personal/money-oriented, clients, open-source
- I can't disclose the client's name on that website due to NDA
So I need to store:
- path to the repository
- group name
- vanity name (so "long-name-repo" can become "Long name Repo")
- undisclose (boolean)
- disclose as group name
- disclose as vanity name
An optional flag for the summary, like --undisclose, will reveal the Group/Vanity name; otherwise, undiscloseable stats get re-labelled into the specific group of elements if specified, otherwise a random name will be generated.
At the beginning, the YAML contained only paths, then I needed labels, and I wanted to experiment, that's why I have them as
/path/to/the/repo [group-label][vanity-label]
This structure is ugly AF.
The end goal is to extract stats in terms of "I worked on those things", but:
So I need to store:
An optional flag for the summary, like --undisclose, will reveal the Group/Vanity name; otherwise, undiscloseable stats get re-labelled into the specific group of elements if specified, otherwise a random name will be generated.