BudgetBridge

BudgetBridge is a Web application that simplifies personal finance management by converting diverse bank statement formats into structured, importable data for budgeting tools like YNAB (You Need A Budget), Monarch, or EveryDollar.

Overview

BudgetBridge streamlines the process of importing financial data into your budgeting app. Upload statements in various formats (CSV, QIF, PDF), let the system parse and normalize the data, apply AI-powered categorization, and export clean CSV files ready for import.

Contributing

We welcome contributions! To ensure smooth collaboration:

Before You Start

1. Check existing issues – Browse open issues to see if your idea is already being discussed
2. Open an issue first – For significant changes, create an issue to discuss your proposal before starting work
3. Ask questions – Use GitHub Discussions or issues to clarify requirements

Pull Request Workflow

1. Fork and branch – Create a feature branch from main
2. Keep changes focused – One PR should address one issue or feature
3. Write clear commit messages – Describe what and why, not just how
4. Add tests – Include unit tests for new functionality
5. Update documentation – Keep README and inline docs current
6. Request review – Tag relevant maintainers for review

Code Standards

• Backend (.NET): Follow standard C# conventions, use dependency injection, write testable code
• Frontend (React): Use TypeScript, follow shadcn/ui + Tailwind patterns, implement responsive designs
• AI agents welcome: Our tasks are written to be AI-agent friendly. Feel free to use AI coding assistants, but review all generated code carefully

Communication

• GitHub Issues: Primary channel for bug reports and feature requests
• GitHub Discussions: For questions, ideas, and general discussion
• Pull Request comments: For code-specific discussions during review

What We're Looking For

• Bug fixes
• Feature implementations (check issues labeled good first issue or help wanted)
• Documentation improvements
• Test coverage improvements
• Performance optimizations

What to Avoid

• Large refactors without prior discussion
• Style-only changes (unless fixing consistency issues)
• Breaking changes without clear justification and migration path

License

MIT