This patch is intended to resolve the following issue that appears while
calling `cmake` for submodules from time to time:

    fatal: No tags can describe '<sha>'.
    Try --always, or create some tags.

This happens because the `actions/checkout` GitHub action fetches the
repository with the `--unshallow` option, but it doesn't do the same for
submodules. So this leads to the error above while using `git describe`
for submodules.

This is fixed by converting a shallow submodule to a complete one.

NO_DOC=ci
NO_TEST=circuit
NO_CHANGELOG=ci

This patch finally brings desired testing for static build packages.

How it works:

In a few words, we have two workflow files: calling and callable. The
callable workflow (static_build_pack_test_deploy.yml) is parametrized
and contains all the logic with the building, testing, and deploying
packages. It takes just two inputs: package platform and JSON matrix
for testing. The calling workflow (packaging.yml) just runs callable
one with specific parameters and contains all the logic related to
triggering by events and concurrency.

The static_build_pack_test_deploy.yml workflow consists of three jobs:
`build`, `test`, and `deploy`. Artifacts between jobs are passed via
the `upload-artifact` and `download-artifact` actions. The `test` job
is a matrix one and verifies packages on provided Linux distros passed
through input. After the testing is done, the `deploy` job is intended
to upload packages to repositories on a tag push, which means release
or pre-release.

Note, for starting Docker containers to test packages we use PackPack
images because they have almost all requirements to run tests.

Follows up #8771
Follows up #8840
Follows up #8866

Closes tarantool/tarantool-qa#322

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Run release build ASAN testing inside a Docker container created from
the `tarantool/testing:ubuntu-jammy-clang16` Docker image with Clang 16
installed.

Closes tarantool/tarantool-qa#319

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

I want to receive review request notifications about the changes and let
people know who is responsible to accept them.

NO_CHANGELOG=no code changes
NO_TEST=no code changes
NO_DOC=no code changes

Commit f14cb97d ("ci: update paths in a fuzzing workflow") breaks
fuzzing workflow because one may only define one of `paths` and
`paths-ignore` for a single event. The patch fixes that.

NO_CHANGELOG=ci
NO_DOC=ci
NO_TEST=ci

Module API documentation is described in Doxygen comments in C/C++ files
in src/ directory. No sense to run this job for other changes. The patch
changes paths in workflow accordingly.

NO_CHANGELOG=ci
NO_DOC=ci
NO_TEST=ci

Fuzzing is a heavyweight job, we can reduce a set of paths used for
triggering this job and therefore reduce an overall time of testing in
some cases.

The patch replaces `.github/workflows/**` to
`.github/workflows/fuzzing.yml` because workflows are independent and
changes in other workflows does not affect fuzzing at all and patch adds
Lua files (`**.lua`) to ignores because fuzzing focused on C/C++ code.

NO_CHANGELOG=ci
NO_DOC=ci
NO_TEST=ci

Remove hard-coded compiler version for the `test-release-asan` target
in the .test.mk file.

NO_DOC=make
NO_TEST=make
NO_CHANGELOG=make

Run release build LTO testing inside a Docker container created from the
`tarantool/testing:ubuntu-jammy-clang16` image with Clang 16 installed.

Closes #318

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Run release build testing inside a Docker container created from the
`tarantool/testing:ubuntu-jammy-clang16` image with Clang 16 installed.

Closes #317

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Add code owners for CI-related script and
for github automation directory.

NO_CHANGELOG=no code changes
NO_TEST=no code changes
NO_DOC=no code changes

In order to improve tests of Tarantool core
assign dedicated team to perform review of each
and every change.

NO_CHANGELOG=no code changes
NO_TEST=no code changes
NO_DOC=no code changes

Modify `actions/pack-and-deploy/action.yml` for creating static build
packages and deploying them to the repository via RWS service. Modify
`workflows/static_build_packaging.yml` for using this action.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Update artifact paths in the static_build_packaging.yml workflow due to
fixing the issue with `OUTPUT_DIR` in the previous commit.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Tarantool 3.0.0 is not going to be distributed as a set of packages for
specific distros. Instead, it is planned to have a few `deb` and `rpm`
packages with a statically compiled Tarantool binary inside, which will
work on almost any distro. Also, we drop building packages with GC32.
Now only GC64 packages will be shipped.

Static build packaging was added at #8771.

NO_DOC=ci
NO_TEST=ci

The created packages can be found in the job artifacts.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Co-authored-by: Yaroslav Lobankov <y.lobankov@tarantool.org>

This patch fixes the crontab expression in the
Lango team stale PRs workflow, so it runs not every minute,
but every hour.

Also, python version is updated to 3.11, since the script is
reliant onto `datetime.fromisoformat' changes, that were
introduced in that version.

NO_DOC=Workflow fix
NO_TEST=Workflow fix
NO_CHANGELOG=Workflow fix

The 2.11.0 release is out now.

It reverts PR #8367.

NO_DOC=no code changes
NO_CHANGELOG=see NO_DOC
NO_TEST=see NO_DOC

It was decided to include the `osx_debug.yml` and `osx_release.yml`
workflows to the default tests run (without the `full-ci` label).
Now we can get test results for macOS faster and without an extra
load on CI.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

If one uses mail notifications about failed ci workflows, he can see
tons of the following notifications for his fork of Tarantool:
| [Buristan/tarantool] Run failed: lango-stale-reviews - master
This job failed due to unknown credentials.

This patch adds the condition to run this workflow only for main
Tarantool repo.

NO_DOC=Workflow fix
NO_TEST=Workflow fix
NO_CHANGELOG=Workflow fix

Fix the `test-sdk` job in the `submodule_update.yml` workflow according
to the new name policy for supported branches (2.10 -> release/2.10,
2.11 -> release/2.11).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

README.md in the `report-job-status` action was fixed in accordance
with the new name policy for supported branches (2.10 -> release/2.10,
2.11 -> release/2.11).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

The condition for uploading test artifact to S3 was fixed in accordance
with the new name policy for supported branches (2.10 -> release/2.10,
2.11 -> release/2.11).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

The condition for workflow concurrency was fixed in accordance with
the new name policy for supported branches (2.10 -> release/2.10,
2.11 -> release/2.11).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

The push trigger in the submodule_update.yml workflow was fixed
in accordance with the new name policy for supported branches
(2.10 -> release/2.10, 2.11 -> release/2.11).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

The push trigger for branches matching to the `[0-9].[0-9]+` pattern
was removed due to changing the name policy for supported branches
(2.10 -> release/2.10, 2.11 -> release/2.11).

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

- Rename the workflow into `publish-module-api-doc` to be consistent
  with other workflow names.
- Refactor workflow triggers.
- Run the workflow only on push to the tarantool/tarantool repository
  or on pull request if the 'notest' label is not set.
- Simplify condition for publishing generated API documentation.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

After this patch, the workaround for LuaJIT profiling tests to
avoid runner's shutdown due to no space left on the disk is going
to be used in all relevant workflows. Previously, we applied it
only for the coverage test, but we noticed that other jobs may be
affected as well after tarantool/tarantool#8737 is merged.

Follows up tarantool/tarantool#7472

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

The next major release of Tarantool (3.0.0) will not support Cartridge.
So tet's be ready in advance. This patch removes the cartridge and crud
integration test runs to make the integration tests pass for #8289.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Default token for actions provided by GitHub lacks
read and write permissions for private projects. This
commit changes the token used for the stale PRs workflow
to the dedicated token with needed permissions.

NO_DOC=Workflow fix
NO_TEST=Workflow fix
NO_CHANGELOG=Workflow fix

The setup-python action defaults to searching for
a dependency file (requirements.txt or pyproject.toml
for pip, Pipfile.lock for pipenv or poetry.lock for
poetry) in the repository, and uses its hash as a
part of the cache key. We don't have one, so the
caching option is disabled.

NO_DOC=Workflow fix
NO_TEST=Workflow fix
NO_CHANGELOG=Workflow fix

This patch adds a Python script, that uses GitHub's GraphQL
API to provide automatic last update date for PR items on
any specified GitHub ProjectsV2 board.

Since there is no versatile enough  way to automate a
GitHub ProjectV2 by its own means, that is done via
standard mechanism of on schedule workflow, which runs
the script every hour.

NO_DOC=workflow
NO_TEST=workflow
NO_CHANGELOG=workflow

Provide the `report-job-status` action with the `job-name` param to get
the direct link to the failed job in the failure message.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

Call the `checkout` action with the `path` param to avoid the following
error:

  Error: File was unable to be removed Error: EACCES: permission denied,
  unlink '/home/runner/work/tarantool/tarantool/build-out/csv_fuzzer'

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

We have the limited hardware resources with macOS 12, and full testing
is time-consuming. So let's check only the release build on the x86_64
platform.

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

To make changelog preparation less stressful let's pass each and every
change to changelogs/ directly through the doc team.

NO_CHANGELOG=no code changes
NO_TEST=no code changes
NO_DOC=no code changes

* Add an extra step that should be considered as a workaround for the
  runner agent (ChristopherHX/github-act-runner) that is used on FreeBSD
  machines. Without it, env.ARTIFACT_EXISTS will be undefined for some
  reason.

* In the s3-upload-artifact action change `if: env.ARTIFACT_EXISTS` to
  `if: env.ARTIFACT_EXISTS == 'true'` to be compatible with the FreeBSD
  runner agent.

Follows up tarantool/multivac#116

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci

NO_DOC=ci
NO_TEST=ci
NO_CHANGELOG=ci