Fix privacy-check failing on empty author range - #6
Merged
Conversation
Main push CI fetched origin/main, then HEAD --not origin/main was empty and counted as a personal-email failure. Skip a base that is HEAD, honor github.event.before, and do not fail when there is nothing new to scan. Co-authored-by: Bryan @ FnFirst <function1st@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Main CI has been red on every push: after fetching
origin/main,HEAD --not origin/mainis empty andprivacy-check.pytreated that as a personal-email failure (no commits to check).github.event.beforeso a main push still scans the new commitsGITHUB_BASE_REFso it actually rejects a personal emailThis is why the job you linked failed after PR #5 merged.