Skip to content

DevBranch.md

Latest commit

 

History

History
68 lines (43 loc) · 4.19 KB

DevBranch.md

File metadata and controls

68 lines (43 loc) · 4.19 KB

Development branch

Attention: Dev branch is for the further development of AAPS only. Se debe utilizar en un teléfono aparte para probar no para un lazo actual.

The most stable version of AAPS to use is that in the Master branch. Se aconseja que permanezca en la rama maestra.

The dev version of AAPS is only for developers and testers comfortable dealing with stacktraces, looking through log files and maybe firing up the debugger to produce bug reports that are helpful to the developers (in short: people that know what they are doing without being assisted!). Por lo tanto, muchas características inacabadas están inhabilitadas. To enable these features enter Engineering Mode by creating a file named engineering_mode in directory /AAPS/extra . Enabling the engineering mode might break the loop entirely.

Sin embargo, la rama de desarrollo es un buen lugar para ver qué características se están probando y para ayudar a resolver los errores y dar información sobre cómo funcionan las nuevas funciones en la práctica. A menudo, la gente probará la rama Dev en un teléfono viejo y la bomba hasta que estén seguros de que es estable - cualquier uso de la misma es a su propio riesgo. Al probar cualquier característica nueva, recuerde que está eligiendo probar una característica aún-en-desarrollo. Haga lo mismo a su propio riesgo & con la debida diligencia para mantenerte a salvo.

Si encuentra un error o cree que ha ocurrido algo incorrecto al utilizar la ramificación de desarrollo, visualice la pestaña de problemas para comprobar si alguien más lo ha encontrado o si lo ha añadido si no lo ha hecho. The more information you can share here the better (don't forget you may need to share your log files. The new features can also be discussed on discord.

A dev version has an expiration date. This seems inconvenient when using it satisfactorily, but serves a purpose. When a single dev version doing the rounds, it is easier to keep track of bugs that people are reporting. The developers do not want to be in a position where there are three versions of dev in the wild where bugs are fixed in some and not others, and people continue to report the fixed ones.

(branch-ci-test)=

Test a specific branch (branch-ci)

To build a test branch, select branch-ci, which allows you to choose a specific branch for APK creation. You can use this method when you need to test the dev branch.

aaps_ci_branch_ci1

aaps_ci_branch_ci2

(github-pr-test)=

Test items in a pull request (GitHub CI actions deploy)

Available from 3.3.2.1.dev

  • Suitable for testers or those helping with testing.
.. raw:: html

    <!--crowdin: exclude-->
    <div align="center" style="max-width: 360px; margin: auto; margin-bottom: 2em;">
      <div style="position: relative; width: 100%; aspect-ratio: 9/16;">
        <iframe
          src="https://www.dailymotion.com/embed/video/x9rdx1q"
          style="position: absolute; top: 0; left: 0; width: 100%; height: 100%;"
          frameborder="0"
          allowfullscreen>
        </iframe>
      </div>
    </div>

aaps_ci_pr_ci

  • PR number: Please enter the PR number that you want to test.

  • PR reference types: PR reference types include two options:

    • head:

    • Fetches the actual content from the PR author’s branch (i.e., the original commit history without any merge operations).

    • This is equivalent to the original state of the PR branch, as if it were fetched directly from a fork or feature branch.

    • merge:

    • Fetches the result of GitHub’s pre-simulated merge of the PR into the target branch (e.g., dev).

    • This is a virtual merge commit automatically created by GitHub.

    • This commit only exists when the PR has no conflicts and is mergeable.

    • variant:

    • Please refer to