Your First PR

Contributing to FlowInquiry isn’t just about code—it’s about joining a community that values quality, purpose, and growth.

The maintainers of FlowInquiry are committed to building a world-class service that delivers real value to customers. Behind every feature, there’s careful attention to detail, clean architecture, and well-crafted code. We care deeply about the product experience and the long-term maintainability of the project.

By contributing to FlowInquiry, you’re helping shape a high-quality open source project built with a strong architectural foundation. Whether you’re a junior developer looking to gain hands-on experience or an experienced engineer who values clean design and long-term maintainability, there’s room for you here.

This is a chance to write meaningful code, share your expertise, and collaborate on real-world challenges alongside a community that values thoughtful engineering. Your contribution—big or small—helps push FlowInquiry forward.

Whether it’s fixing a bug, improving the documentation, or introducing a new feature, your first pull request is a meaningful step. We’re here to support you on that journey.

Welcome aboard—and thank you for making FlowInquiry better!

🚀 Getting Started

FlowInquiry is an open-source project with two main repositories:

Frontend (Next.js): https://github.com/flowinquiry/flowinquiry-frontend
Backend (Spring Boot): https://github.com/flowinquiry/flowinquiry-server

Whether you’re interested in UI development or backend logic and APIs, there’s a place for you to contribute.

Before contributing, we highly recommend reading our Development Guidelines. It covers project structure, code style, commit conventions, and other important practices that help us maintain a clean and consistent codebase.

1. Fork the Repositories

Start by forking the repository you’d like to contribute to (or both).

Go to the GitHub page of the relevant repo and click the Fork button in the top-right corner.

2. Clone Your Fork

Clone your forked repository to your local machine:

Frontend:


git clone [email protected]:flowinquiry/flowinquiry-frontend.git
cd flowinquiry-frontend

Backend:


git clone [email protected]:flowinquiry/flowinquiry-server.git
cd flowinquiry-server

3. Create a New Branch

Always create a new branch for your changes:


git checkout -b your-feature-name

4. Make Your Changes

Make your updates — whether it’s fixing a bug, improving documentation, or adding a new feature.

5. Commit and Push


git add .
git commit -m "Describe your changes"
git push origin your-feature-name

6. Open a Pull Request

Once you’ve pushed your changes, go to your fork on GitHub and click “Compare & pull request”. Add a clear description of your changes, link any related issues, and submit your PR.

✅ What Happens Next

Your pull request will be reviewed by a maintainer or experienced contributor.
We may request changes to match our standards or align with the project architecture.
Reviews are collaborative — feel free to ask questions or discuss decisions.
We aim to review PRs in a timely manner and appreciate your patience!

📄 Contributor License Agreement (CLA)

If this is your first time contributing to FlowInquiry, you’ll be prompted by a GitHub bot to sign the Contributor License Agreement (CLA) when you open the PR.

Your PR cannot be merged until the CLA is signed. It only needs to be signed once, and the process is quick and automated.

Need help finding a place to contribute? Check out our good first issues or backend issues .

We’re excited to see your contribution — welcome to the FlowInquiry community!