Skip to content
Snippets Groups Projects
Select Git revision
  • a1cff7e3bb01b345dd1cbb896282f8065b969c65
  • master default protected
  • 313_ci_image
  • 311_gtest_fixes
  • set_UniversalDividendApi_in_RuntimeApiCollection
  • tuxmain/fix-change-owner-key
  • network/gtest-1000 protected
  • upgradable-multisig
  • runtime/gtest-1000
  • network/gdev-800 protected
  • cgeek/issue-297-cpu
  • gdev-800-tests
  • update-docker-compose-rpc-squid-names
  • fix-252
  • 1000i100-test
  • hugo/tmp-0.9.1
  • network/gdev-803 protected
  • hugo/endpoint-gossip
  • network/gdev-802 protected
  • hugo/distance-precompute
  • network/gdev-900 protected
  • gtest-1000-0.11.1 protected
  • gtest-1000-0.11.0 protected
  • gtest-1000 protected
  • gdev-900-0.10.1 protected
  • gdev-900-0.10.0 protected
  • gdev-900-0.9.2 protected
  • gdev-800-0.8.0 protected
  • gdev-900-0.9.1 protected
  • gdev-900-0.9.0 protected
  • gdev-803 protected
  • gdev-802 protected
  • runtime-801 protected
  • gdev-800 protected
  • runtime-800-bis protected
  • runtime-800 protected
  • runtime-800-backup protected
  • runtime-701 protected
  • runtime-700 protected
  • runtime-600 protected
  • runtime-500 protected
41 results

offences_tests.rs

Blame
    • git-conventions.md 6.46 KiB

    Duniter git conventions

    TL;DR summary of this page, workflow instructions

    The summary gives an overview of the rules described below. Reading it will help you to dive into the details.

    • draft work must be prefixed by "WIP" (work in progress)
    • the naming of final commits must comply with the template type(scope): action subject
    • one should communicate with developers through dedicated spaces
    • integrating a contribution can only be done via a merge request on our gitlab option and since the following critera are fullfilled
      • branch up to date with master branch (except hotfixes, see the hotfix section)
      • idiomatic code formatting, automated tests passed successfully
      • clean commit history, understandable and concise
      • contribution approved by a reviewer

    Naming commits

    Every commit must comply with conventional commit specification v1.0.0.

    The commit name has to be meaningful in the context of commit history reread. It should not make reference to a specific MR or discussion. Among other, commit history is used in changlogs and to track the project progress, that's why it has to be self-explanatory. If you have a new need, please contact the main developers to add a type together.

    Update strategy

    We only use rebases, merges are strictly fordbidden !

    Every time the master branch is updated, you must rebase each of your working branch on it. For each of them: