Skip to content

Latest commit

 

History

History
65 lines (46 loc) · 2.86 KB

File metadata and controls

65 lines (46 loc) · 2.86 KB

This document specify hints and good practices for source code contributions.

AndroidAPS is community effort and all contributions are welcome! If you wish help us improving AAPS - please read and try to adhere to this guidelines, to make the development and process of change approval as smooth as possible :)

General rules

AI-generated contributions

AndroidAPS is safety-critical software. AI-generated pull requests are not welcome.

Verifying and reviewing AI-generated code reliably takes maintainers more time than the AI took to produce it, and unverified code is a risk we cannot accept in this project.

If you want to use AI to help analyze the codebase or investigate a problem, the correct way to contribute is:

  • Open an Issue describing the problem and include the AI findings as analysis/context
  • Leave the actual coding and the fix to the repository maintainers

This keeps the analysis useful while making sure every change to the code is written and verified by people who understand and own it.

Development guidelines

Coding conventions

  1. Use Android Studio with default indents (4 chars, use spaces)
  2. Use autoformat feature CTRL-ALT-L in every changed file before commit

Committing Changes / Pull Requests

  1. Make a fork of repository on GitHub (be aware to uncheck the box "Copy the master branch only")
  2. Create separate branch for each feature, branch from most recent dev
  3. Commit all changes to your fork
  4. When ready, rebase on top of dev and make Pull Request to main repo

Naming Conventions for Pull Requests / Branches

TODO

Translations

Hints

  • Start small, it is easier to review smaller changes that affect fewer parts of code
  • Take a look into Issues list (https://github.com/nightscout/AndroidAPS/issues) - maybe there is something you can fix or implement
  • For new features, make sure there is Issue to track progress and have on-topic discussion
  • Reach out to community, discuss idea on Discord (https://discord.gg/4fQUWHZ4Mw)
  • Speak with other developers to minimize merge conflicts. Find out who worked, working or plan to work on specific issue or part of app