GitHub Issue Structure for Personal Finance Tracking When building financial analysis systems, separate confidential data/config (private personal repo) from algorithms/logic (shared/public repo). Create the tracking issue in the data repo with clear references to algorithm repos where implementation lives. This enables sensitive portfolio info to stay private while keeping reusable code modular and potentially shareable. Flag browser access limitations early (e.g., Fidelity blocked by safety extensions) and establish manual data handoff workflows. ---