-
Notifications
You must be signed in to change notification settings - Fork 28
Hackathon Guide
Welcome to our Hackathon! π Below, you'll find a curated list of GitHub issues categorized by area of expertise. Feel free to choose one that aligns with your skills and interests.
- Find an Issue: Browse the categorized list below and select an issue to work on.
- Fork the Repository: Create a fork of the project repository.
- Create a Feature Branch: Work on your solution in a dedicated branch.
- Follow Conventional Commits: Ensure commit messages follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/).
- Write Unit Tests: Aim for 80% test coverage where possible.
- Pass Build Checks: Ensure that all CI/CD checks pass before submitting.
- Submit a Pull Request: Once you're ready, submit a Pull Request (PR) from your fork.
Issues related to frontend development, styling, and user experience.
- Issue #1584 - Upgrade React
- Issue #2124 - Add support for i18n
- Issue #2491 - Ctrl+Alt+Delete
- Issue #2486 - Error Messages Truncated
Issues related to backend services, API design, and data processing.
- Issue #499 - Enhance Logging Capability in Console
- Issue #511 - Add Config Option to Disable Encryption
- Issue #485 - Update/Replace Dependency
Issues related to cloud deployment, CI/CD, and infrastructure automation.
β
Use meaningful branch names (feature/add-dark-mode, fix/api-response-time).
β
Ensure all CI/CD checks pass before submitting a PR.
β
Follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) for commit messages.
β
Include unit tests for all new functionality.
β
Tag your PR with hackathon for easy tracking.
π‘ Need help? Join our Discord group: Device Management Toolkit in the #hackathon channel. Post your questions there and reach out to our team!
Happy hacking! π