[PR #1321] [MERGED] [IMPROVEMENT] Add bazel build to Github Actions. #2097

New Issue

claunia · 2026-01-29T17:20:17Z

claunia commented

2026-01-29 17:20:17 +00:00

📋 Pull Request Information

Original PR: https://github.com/CCExtractor/ccextractor/pull/1321
Author: @kvshravan
Created: 4/12/2021
Status: ✅ Merged
Merged: 4/12/2021
Merged by: @canihavesomecoffee

Base: master ← Head: bazel-actions

📝 Commits (1)

69f2e3d Add bazel build to Github Actions

📊 Changes

1 file changed (+10 additions, -0 deletions)

View changed files

📝 .github/workflows/build_linux.yml (+10 -0)

📄 Description

In raising this pull request, I confirm the following (please check boxes):

I have read and understood the contributors guide.
I have checked that another pull request for this purpose does not exist.
I have considered, and confirmed that this submission will be valuable to others.
I accept that this submission may not be used, and the pull request closed at the will of the maintainer.
I give this submission freely, and claim no ownership to its content.

My familiarity with the project is as follows (check one):

I have never used CCExtractor.
I have used CCExtractor just a couple of times.
I absolutely love CCExtractor, but have not contributed previously.
I am an active contributor to CCExtractor.

As discussed @cfsmp3 , I've added bazel build to Github actions for linux. So whenever a new pr comes from now it'll be tested for bazel build and only if all of the builds which now includes bazel pass, only then a test will be ran for a pr via sample-platform (yet to be done in this year's GSoC).
CC @canihavesomecoffee

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/CCExtractor/ccextractor/pull/1321 **Author:** [@kvshravan](https://github.com/kvshravan) **Created:** 4/12/2021 **Status:** ✅ Merged **Merged:** 4/12/2021 **Merged by:** [@canihavesomecoffee](https://github.com/canihavesomecoffee) **Base:** `master` ← **Head:** `bazel-actions` --- ### 📝 Commits (1) - [`69f2e3d`](https://github.com/CCExtractor/ccextractor/commit/69f2e3d8b856be2b0695c9e86b93c1f2fdac6147) Add bazel build to Github Actions ### 📊 Changes **1 file changed** (+10 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/build_linux.yml` (+10 -0) </details> ### 📄 Description **In raising this pull request, I confirm the following (please check boxes):** - [x] I have read and understood the [contributors guide](https://github.com/CCExtractor/ccextractor/blob/master/.github/CONTRIBUTING.md). - [x] I have checked that another pull request for this purpose does not exist. - [x] I have considered, and confirmed that this submission will be valuable to others. - [x] I accept that this submission may not be used, and the pull request closed at the will of the maintainer. - [x] I give this submission freely, and claim no ownership to its content. **My familiarity with the project is as follows (check one):** - [ ] I have never used CCExtractor. - [ ] I have used CCExtractor just a couple of times. - [ ] I absolutely love CCExtractor, but have not contributed previously. - [x] I am an active contributor to CCExtractor. --- As discussed @cfsmp3 , I've added bazel build to Github actions for linux. So whenever a new pr comes from now it'll be tested for bazel build and only if all of the builds which now includes bazel pass, only then a test will be ran for a pr via sample-platform (yet to be done in this year's GSoC). CC @canihavesomecoffee --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

claunia added the pull-request label 2026-01-29 17:20:17 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/ccextractor#2097