Thank you for helping build Nepali-first developer tools. Contributions can improve the language engine, Android interface, accessibility, examples, tests, documentation, or release process.
Please search existing issues and pull requests before opening a new one. For substantial changes, open an issue first so the design can be discussed before implementation begins.
- Install Android Studio, Android SDK Platform 36, Build Tools 36, and Java 21.
- Clone the repository and open it in Android Studio.
- Copy
.env.exampleto.envwhen AI-backed features are needed. - Never commit API keys, keystores, generated build folders, or personal machine configuration.
Use a focused branch for each change:
git checkout -b feat/short-description
./gradlew test
./gradlew assembleDebug
git diff --checkKeep pull requests small enough to review. Explain the motivation, summarize the implementation, describe testing, and include screenshots or a short recording for visible UI changes.
A new language feature should include an example program, lexer/token changes when needed, parser or AST coverage, interpreter behavior, linter behavior where appropriate, and documentation. Favor clear diagnostics and predictable behavior over clever shortcuts.
Use concise imperative messages such as Add list literal parsing or Improve file manager empty state. Avoid mixing unrelated refactors with feature changes.
- The change is scoped and documented.
- Tests or a clear manual verification process are included.
./gradlew testpasses locally when applicable../gradlew assembleDebugsucceeds.- No secrets, keystores, or generated build artifacts are included.
- User-facing strings and accessibility descriptions are considered.
- Screenshots are included for meaningful UI changes.
Open a discussion or issue with a clear title, reproduction steps, expected behavior, and relevant logs. Please follow the Code of Conduct.