Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Mike Kruskal	f1e746c491	Migrate remaining Windows tests to GHA PiperOrigin-RevId: 506766851	2 years ago
Mike Kruskal	6816da50cf	Migrate non-Linux C++ tests to GHA actions PiperOrigin-RevId: 506683178	2 years ago
Mike Kruskal	a138e54582	Migrate Python and Ruby Linux tests to GHA actions PiperOrigin-RevId: 506449977	2 years ago
Mike Kruskal	2b4e4260f0	Migrate to composite GHA actions (#11718 ) This migrates from reusable workflows to composite GHA actions. This has the following advantages: 1) We can split them into smaller, easier to reason about chunks 2) We can reuse them more freely between each other and workflows 3) They don't complicate the job names 4) In theory they'll be easier to test in isolation. While composite actions can't be unit-tested, we can easily break them up into nodejs or docker actions that can be. As a proof of concept, some of our non-Bazel tests are migrated to GHA as well (CMake + Composer) Closes #11718 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11718 from protocolbuffers:gha-actions 5403307bc00616e94816aa460813939d8f37a1bd PiperOrigin-RevId: 506375417	2 years ago
Mike Kruskal	de903d41fc	Migrate Bazel C++ Linux tests to Github Actions (#11702 ) This is a proof of concept that we can experiment with before migrating all of our Kokoro tests to GHA. In addition to the migration, this builds out infrastructure for safe handling of both external and internal contributions. Two of the existing GHA workflows have also been migrated to this system to unify how we handle testing. To test the new workflow introduced here, you can open PRs to the `gha` branch. This feature branch acts as a staging area for GHA. PRs opened up from this repo will automatically have all tests run on each commit. We will also run them all as post-submits, and continuously on a daily schedule. PRs opened from forked repos will need per-commit approval for each test run, which can be given by adding the `safe for tests` label. Examples (failures are intentional to show that the PR code is being tested): - Internal PR: https://github.com/protocolbuffers/protobuf/pull/11679 - Fork PR (approved): https://github.com/protocolbuffers/protobuf/pull/11685 - Fork PR (rejected): https://github.com/protocolbuffers/protobuf/pull/11683 - External PR: https://github.com/protocolbuffers/protobuf/pull/11695 Closes #11702 COPYBARA_INTEGRATE_REVIEW=https://github.com/protocolbuffers/protobuf/pull/11702 from protocolbuffers:gha `f3a2663896` PiperOrigin-RevId: 506169444	2 years ago