Squashed merges and CI checks #39074
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
We have some CI checks that are required on a protected branch.
Developers submit PRs against the protected branch and can only either squash+merge or rebase if all CI checks pass. That's working as expected.
We discovered an issue with commits' email addresses. We have a CI check that verifies that email addresses are set to the proper @example.tld domain. That sometimes is being bypassed on squashes through the UI when users have configured their accounts to not expose their emails and use that @noreply.github.com address.
CI passes because it sees all the correct @example.tld commits in the branch. Then the user squash/merges all those commits into a single one through the UI and the final commits has @noreply.github.com, rendering the CI check essentially useless. Now our protected branch has "bad" commits.
Is this a situation others have faced before? Any workarounds or would this be a feature request of sorts?
Beta Was this translation helpful? Give feedback.
All reactions