Skip to content

imtabako/ton

This branch is 571 commits behind ton-blockchain/ton:master.

Folders and files

NameName
Last commit message
Last commit date
Nov 22, 2022
Sep 7, 2019
Aug 22, 2022
Feb 10, 2021
Aug 8, 2022
Apr 10, 2020
Aug 19, 2021
Oct 12, 2022
Feb 27, 2021
Jul 6, 2020
Aug 15, 2022
Nov 22, 2022
Apr 10, 2020
Oct 3, 2022
Sep 29, 2022
Apr 10, 2020
Apr 10, 2020
Aug 15, 2022
Aug 30, 2022
Apr 10, 2020
Oct 3, 2022
Sep 29, 2022
Oct 3, 2022
Jun 7, 2022
Jun 7, 2022
May 27, 2020
Jan 7, 2021
Jul 6, 2020
Jul 6, 2020
Jul 6, 2020
Sep 14, 2022
Jul 10, 2020
Aug 18, 2022
Jun 27, 2022
May 27, 2020
Sep 30, 2022
Aug 8, 2022
Sep 20, 2022
Feb 27, 2021
Sep 15, 2022
Sep 18, 2022
Sep 19, 2022
Sep 21, 2022
Sep 7, 2019
Sep 7, 2019
Sep 7, 2019
Jun 6, 2022
Sep 7, 2019
Sep 21, 2022
Oct 6, 2022
Feb 6, 2020
Feb 2, 2020
Sep 7, 2019
Oct 12, 2022
Feb 27, 2021
Feb 27, 2021
Feb 27, 2021
Sep 7, 2019

Repository files navigation

TON Overflow Group Stack Overflow Group Telegram Foundation Group Telegram Community Group Twitter Group

TON

Main TON monorepo, which includes the code of the node/validator, lite-client, tonlib, FunC compiler, etc.

Updates flow:

  • master branch - mainnet is running on this stable branch.

    Only emergency updates, urgent updates, or updates that do not affect the main codebase (GitHub workflows / docker images / documentation) are committed directly to this branch.

  • testnet branch - testnet is running on this branch. The branch contains a set of new updates. After testing, the testnet branch is merged into the master branch and then a new set of updates is added to testnet branch.

  • backlog - other branches that are candidates to getting into the testnet branch in the next iteration.

Usually, the response to your pull request will indicate which section it falls into.

"Soft" Pull Request rules

  • Thou shall not merge your own PRs, at least one person should review the PR and merge it (4-eyes rule)
  • Thou shall make sure that workflows are cleanly completed for your PR before considering merge

Workflows responsibility

If a CI workflow fails not because of your changes but workflow issues, try to fix it yourself or contact one of the persons listed below via Telegram messenger:

  • C/C++ CI (ccpp-linux.yml): TBD
  • C/C++ CI Win64 Compile (ccpp-win64.yml): TBD

About

Main TON monorepo

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • C++ 97.3%
  • CMake 1.8%
  • Java 0.3%
  • PHP 0.2%
  • Python 0.2%
  • C 0.1%
  • Other 0.1%