These three PRs should be merged in the following order to avoid conflicts:
Merge First
- Creates
src/config/index.js- centralized configuration module - Modifies multiple files to use centralized config
- Base for other changes
Merge Second
- Creates service layer (DonationService, WalletService, StatsService)
- Refactors controllers to be thin orchestration layers
- Depends on #240's centralized config
Merge Last
- Deletes
src/config/envValidation.js(replaced by #240's centralized config) - Removes unused stellar service modules
- Removes dead code and unused functions
- Depends on both #240 and #241
If merged in order, conflicts will be minimal:
- After #240 merges: #241 and #242 may need rebasing
- After #241 merges: #242 may need rebasing
- #242 should merge cleanly after #240 and #241
If PRs are already created, you can:
- Merge #240 to main
- Rebase #241 on main:
git rebase origin/main - Merge #241 to main
- Rebase #242 on main:
git rebase origin/main - Merge #242 to main
src/config/envValidation.js- Deleted in #242 (this is intentional, not a conflict)src/routes/donation.js- Modified in #241, may conflict with #242src/routes/stats.js- Modified in #241, may conflict with #242src/routes/wallet.js- Modified in #241, may conflict with #242src/config/index.js- Created in #240, modified in #242
GitHub shows src/config/envValidation.js as a conflict because:
- Main branch has this file
- PR #242 deletes this file
This is NOT a real conflict - it's the intended behavior. The file is obsolete and should be deleted. When #242 merges, the file will be properly removed from main.
Merge in order: #240 → #241 → #242
This ensures each PR builds on the previous one's changes and minimizes conflicts.