<commit_before>
# future plans

- todo:
   - consider delegating `sync` operations all the way up the bases tree
   - redirect builtin commands stderr to an `error.log` file
   - introduce 'epic' level, capable of aggregating teams *or* features
   - ~~allow overriding the base branch in the 'feature' subcommand~~
   - ~~generalize prompting in the terminal to encapsulate all that 
   verbosity in git-flux-init~~
   - ~~talk about the option to open-source it~~
   - unit tests: explore these libs (ordered by # of stars in github)
      - [bats][1]
      - [assert.sh][2]
      - [shunit2][3]
      - [epoxy][4]
      - [bashtest][5]

- document:
   - an overview of the git-flux model, specifically the levels.
   - elaborate on teams and the ability to switch teams with the `join` action
   - the fact that git-flux addresses some of the issues in git-flow 
   (e.g. we never use `--no-ff`, all merges are done with default strategy)

- exposure:
   - document it well
   - write unit tests
   - search/replace any hard references to the repo url
   - update the docs on setup to use the enterprise form:
   ```sh
   curl -H 'Authorization: token [some_token_with_lots_of_characters]' \
       -H 'Accept: application/vnd.github.v3.raw' \
       -O -L https://lpgithub.dev.lprnd.net/raw/eliranm/git-flux/master/bin/setup.sh
   ```
   - write a blog post (contact vladi regarding the dev-blogs platform)<commit_msg>add todo<commit_after>
# future plans

- todo:
   - create 'gitflux-config' wrapper
   - consider delegating `sync` operations all the way up the bases tree
   - redirect builtin commands stderr to an `error.log` file
   - introduce 'epic' level, capable of aggregating teams *or* features
   - ~~allow overriding the base branch in the 'feature' subcommand~~
   - ~~generalize prompting in the terminal to encapsulate all that 
   verbosity in git-flux-init~~
   - ~~talk about the option to open-source it~~
   - unit tests: explore these libs (ordered by # of stars in github)
      - [bats][1]
      - [assert.sh][2]
      - [shunit2][3]
      - [epoxy][4]
      - [bashtest][5]

- document:
   - an overview of the git-flux model, specifically the levels.
   - elaborate on teams and the ability to switch teams with the `join` action
   - the fact that git-flux addresses some of the issues in git-flow 
   (e.g. we never use `--no-ff`, all merges are done with default strategy)

- exposure:
   - document it well
   - write unit tests
   - search/replace any hard references to the repo url
   - update the docs on setup to use the enterprise form:
   ```sh
   curl -H 'Authorization: token [some_token_with_lots_of_characters]' \
       -H 'Accept: application/vnd.github.v3.raw' \
       -O -L https://lpgithub.dev.lprnd.net/raw/eliranm/git-flux/master/bin/setup.sh
   ```
   - write a blog post (contact vladi regarding the dev-blogs platform)
{'fraction_non_alphanumeric': 0.10013908205841446, 'fraction_numerical': 0.004867872044506259, 'mean_word_length': 2.861744966442953, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2162064', 'n_tokens_mistral': 900, 'n_tokens_neox': 873, 'n_words': 341}