Thank you for your interest in contributing to NexaFx! 🚀 We welcome contributions from the community and appreciate your efforts to improve the project. Please follow the guidelines below to ensure a smooth collaboration.
Instead, provide a clear explanation of your approach, which includes:
- A brief introduction about yourself.
- A concise plan outlining how you will address the issue (3–6 lines max).
- Your estimated completion time (ETA).
How to Contribute🤝
To ensure consistency and improve the review process, we've implemented a PR template. When creating a pull request, please:
-
Follow the PR template that automatically loads when you create a new PR.
-
Fill out all relevant sections of the template.
-
Ensure your PR description clearly communicates the changes you've made.
-
Include screenshots or recordings when applicable.
-
Link to any related issues using keywords like "Closes #123" or "Fixes #123"
The template location is at .github/PULL_REQUEST_TEMPLATE.md and provides a structured format to help maintainers understand and review your contribution more efficiently.
Apply for an Issue
- Look for an open issue and comment expressing your interest in working on it.
- Wait for the maintainer to assign the issue to you.
- Remember to apply only if you can solve the issue. Again, In the comment, Add a quick introduction about yourself, The ETA, and how you plan to tackle the issue.
Ensure you have the following installed:
- Node.js
- npm
- Git
- Fork the repository on GitHub.
- Clone your fork to your local machine:
git clone https://github.com/your-username/NexaFx-web.git cd Nexafx-web - Add the upstream repository:
git remote add upstream https://github.com/Nexacore-Org/Nexafx-web.git
using npm:
npm installnpm run devThe platform should now be running at http://localhost:3000/.
- Check existing issues before opening a new one to avoid duplicates.
- Describe the problem clearly, including steps to reproduce if it's a bug.
- Label the issue appropriately (e.g., bug, enhancement, documentation).
- Follow the coding standards outlined below.
- Reference related issues in the PR description.
- Ensure your code is well-tested before submitting.
- Keep pull requests focused on a single change or feature.
- Use a descriptive title and provide necessary context.
- Follow the Airbnb JavaScript Style Guide.
- Use Prettier for code formatting.
- Write meaningful variable and function names.
- Use TypeScript for type safety.
- Keep components modular and reusable.
- Document functions and components where necessary.
- main: Stable, production-ready code.
- dev: Latest development changes.
- feature/xyz: New features.
- bugfix/xyz: Bug fixes.
Use the following format for commit messages:
[type]: [short description]Examples:
feat: add user authentication flow
fix: resolve issue with quiz scoring
chore: update dependencies- Run unit tests before submitting a PR:
npm run test - Check the browser console for runtime errors.
- Use Redux DevTools or React Developer Tools for state debugging.
- Ensure API requests return expected results before making changes.
If you have any questions, feel free to ask in our telegram community https://t.me/Nexafx.
Thank you for contributing!