chore: document remaining discussions

[kabaros]

This is an empty PR to document some of the pending decisions in this repo.

This repo implements:

• move to shared configs (for eslint and prettier) https://dhis2.atlassian.net/browse/LIBS-614
• move eslint to v9 https://dhis2.atlassian.net/browse/LIBS-701
• explore using a monorep https://dhis2.atlassian.net/browse/LIBS-720

Example of a repo using the configs: dhis2/route-manager-app#35

Decisions around Configs

• The script for upgrading existing apps: https://github.com/dhis2/style-configs/blob/main/configs/scripts/install-shared-configs.sh
  • Do we need it more sophisticated? (i.e. try to copy the existing rules)
  • Is it OK to add husky and eslint-staged everywhere?
  • The GH workflows: update the script to change the workflows (it can't be perfect, but at least cover the workflows-platform way of running linting
  • Do we add the script to d2 so we can do something like d2 style-configs migrate...
  • Other script/helpers: a d2 script to bump the configs in consumers?
• Versioning: we bump all configs together right now - is that we want going on
• Do we want to export a wrapper around the configs, i..e create a package @dhis2/style-configs that re-exports @dhis2/config-eslint and @dhis2/config-prettier etc...
  • That makes the consuming apps only install one dependency .. but we're back to cli-style territory? Maybe this can be solved with tooling, i.e. a script/CLI command that bumps all configs

Decisions around the Monorepo

• The use of Changesets
  • We have a CI step now that fails a PR if it doesn't have a change set (this is the recommendation from changeset). Devs can still add an empty changeset if they'd like.
  • Is that enough?
• Maybe different tooling altogether: tools for monorepos? notes#356
• Do we look at migrating other repos here as part of the spike? https://developers.netlify.com/guides/migrating-git-from-multirepo-to-monorepo-without-losing-history/