This is more of an overview, a conceptual framework that your process fits into.
Let’s imagine that you have 2 Production apps, one for Customer A, and one for Customer B, each in its own Anvil repository. They are identical except for some customer-specific detail X, so A’s X and B’s X are different. (X may be a set of Secrets, a database table, a function or module, a logo, etc.)
When you need to update these apps (e.g., for a bug fix), you will need to preserve those distinct copies of feature X. To do that, you will need to know how Anvil represents them and/or refers to them, within each instance of the app, and how an update (e.g., git push) will affect those things. You may need to take steps before and/or after the update. The details will vary depending on how the feature is implemented, but this is the “big picture” that (I hope) every feature fits into.
Sometimes I need to see the trees. Sometimes I need to see the forest in order to understand the trees. 