Tell the difference between a commit produced from a direct push and a commit produced from a PR merge #41717
Replies: 2 comments
-
Push - Force commit(may not verify changes) You can add rules for every branch, so nobody can merge without approval(except the owner) |
Beta Was this translation helpful? Give feedback.
-
🕒 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
I want to run a GitHub action on
push
.I want however to be able to tell the difference between a direct push and a Pull Request merge. (I don't want my workflow to run on the second case)
I have found a workaround, by allowing only Merge with Squash in which case the head commit produced has the following details in the
giuthub.event
Is there any workaround in case I want to avoid squashes?
Beta Was this translation helpful? Give feedback.
All reactions