-
Notifications
You must be signed in to change notification settings - Fork 41
Comparing changes
Open a pull request
base repository: google/effcee
base: e63a164aa0a4
head repository: google/effcee
compare: ae38e040cbb7
- 10 commits
- 13 files changed
- 2 contributors
Commits on Jan 24, 2025
-
Configuration menu - View commit details
-
Copy full SHA for d4bd354 - Browse repository at this point
Copy the full SHA d4bd354View commit details -
Configuration menu - View commit details
-
Copy full SHA for 61f2ce7 - Browse repository at this point
Copy the full SHA 61f2ce7View commit details
Commits on Jan 29, 2025
-
kokoro: Allow linux image to be set by LINUX_BUILDER_IMAGE (#77)
If LINUX_BUILDER_IMAGE is defined, use that as the URL. Otherwise use the old one.
Configuration menu - View commit details
-
Copy full SHA for 12241cb - Browse repository at this point
Copy the full SHA 12241cbView commit details
Commits on Feb 20, 2025
-
kokoro: Add a check-format presubmit job (#79)
It checks C++ code is formatted like clang-format would.
Configuration menu - View commit details
-
Copy full SHA for 72fb04c - Browse repository at this point
Copy the full SHA 72fb04cView commit details -
Configuration menu - View commit details
-
Copy full SHA for eb16bfc - Browse repository at this point
Copy the full SHA eb16bfcView commit details
Commits on Feb 22, 2025
-
Configuration menu - View commit details
-
Copy full SHA for 874b471 - Browse repository at this point
Copy the full SHA 874b471View commit details
Commits on Apr 30, 2025
-
[Kokoro] Use merge-base for format check (#83)
When doing the clang format check, the current branch is compared with main to see which files changed, and if there are any formating issues in those files. This can cause false positives if the current branch is too far behind main. If another PR fixed the formating in main, then that will be flagged as an error because it looks like the current PR will undo that change. The fix is to use the merge-base for main and HEAD to find the first common ancestor of the two to determine which files are changed in the current branch. Bug: crbug.com/414577655
Configuration menu - View commit details
-
Copy full SHA for abcaf70 - Browse repository at this point
Copy the full SHA abcaf70View commit details
Commits on May 5, 2025
-
Set Bazel module version 0.1 (#84)
Bazel changes - Update to Python 3.12 - Set default visibility to private. Only the CHANGES and LICENSE, and 'effcee' library are public. - Set test size to "small"
Configuration menu - View commit details
-
Copy full SHA for 8ce15c4 - Browse repository at this point
Copy the full SHA 8ce15c4View commit details
Commits on Aug 7, 2025
-
kokoro: remove VS 2019 configurations (#85)
Bug: Google-internal crbug.com/437082422
Configuration menu - View commit details
-
Copy full SHA for 514b52e - Browse repository at this point
Copy the full SHA 514b52eView commit details
Commits on Feb 24, 2026
-
chore: Migrate gsutil usage to gcloud storage (#87)
* chore: Migrate gsutil usage to gcloud storage * Update build.sh
Configuration menu - View commit details
-
Copy full SHA for ae38e04 - Browse repository at this point
Copy the full SHA ae38e04View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff e63a164aa0a4...ae38e040cbb7