Thank you for considering contributing to QR Code app! Your contributions are incredibly valuable and help us improve the product.
-
🍴 Fork the Repository: Click the “Fork” button at the top right of the repository page.
https://github.com/chetanr25/qr_code.git
-
📂 Clone Your Fork:
Replaceyour-username
with your GitHub username.git clone https://github.com/<your-username>/qr_code.git cd qr_code
-
📦 Install Dependencies:
flutter pub get
If you encounter a bug, please report it by creating an issue. Include detailed information to help us understand and reproduce the issue:
- Steps to reproduce the bug.
- Expected behavior.
- Actual behavior.
- Screenshots or logs, if applicable.
We welcome new feature ideas! To request a feature, open an issue and provide:
- A clear and descriptive title.
- The motivation for the feature.
- A detailed description of the proposed solution.
- Any alternatives considered.
We appreciate code contributions! To contribute:
-
🌿 Create a Branch:
git checkout -b feature/your-feature-name
-
⚙️ Make Changes:
Implement your changes following the Development Guidelines. -
📥 Commit Changes:
git add . git commit -m "Add feature: your feature name"
-
🚀 Push to Your Fork:
git push origin feature/your-feature-name
-
🔗 Add the Original Repository as a Remote (Upstream)
If you haven’t already added the original repository as a remote, run:git remote add upstream https://github.com/chetanr25/qr_code.git
-
⬇️ Fetch the Latest Changes from Upstream
git fetch upstream
-
🔀 Merge the Latest Changes from Upstream/Main into Your Feature Branch
git checkout feature/your-feature-name git merge upstream/main
-
📤 Create a Pull Request
After merging the latest changes, go to the original repository and open a Pull Request (PR). Provide a clear and descriptive title and a detailed explanation of your changes.
Development Guidelines
- 🧹 Code Style: Follow the Dart Style Guide and Flutter conventions to maintain consistency.
- 📝 Documentation: Update code comments and the
README.md
file as needed to reflect your changes.
For questions or further assistance, feel free to reach out by opening an issue or contacting the maintainers directly.
We appreciate your contributions and look forward to collaborating with you!