Skip to content

Sync with Pro - #528

Closed
semgrep-ci[bot] wants to merge 1 commit into
mainfrom
sync-with-pro-1785111941
Closed

Sync with Pro#528
semgrep-ci[bot] wants to merge 1 commit into
mainfrom
sync-with-pro-1785111941

Conversation

@semgrep-ci

@semgrep-ci semgrep-ci Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor 
Syncing Pro revision: 4c79747fe8f74e31c98d61fb3a1ebaec6abf5c81
OSS repo was last synced with Pro commit: 2f8c22c20f6df12f2f207455624d67eb08b49a1f
Synchronizing OSS repo with Pro commit 4c79747fe8f74e31c98d61fb3a1ebaec6abf5c81
There are 8 commit(s) to sync.
Syncing...
* 45b482f77ac fix(ci): stop pipefail+grep -q from silently skipping CI on large PRs (#6805)
* Skipping (empty) d8aa1dcfd18
* Skipping (empty) 3727ab16550
* Skipping (empty) a55f325cdb0
* Skipping (empty) 23bc7994f47
* Skipping (empty) 1466d3612df
* Skipping (empty) 719e9ee3c98
* Skipping (empty) 4c79747fe8f
Success!

@ajbt200128 GitHub Actions Bot
fix(ci): stop pipefail+grep -q from silently skipping CI on large PRs (…
ca5f280 
…semgrep/semgrep-proprietary#6805)

In some of the above very large PRs I was running into an issue where grep would die and then it would say no changes needed.

Test plan:

CI in above PR builds docker images (confirmed this)

synced from Pro 45b482f77ac0ec38e9be4aca042ae971c2f0b659
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@yosefAlsuhaibani @ajbt200128