Squash Merge Bug

[supermanko1102]

Select Topic Area

Bug

Body

Dear GitHub Support Team,

I am writing to report an issue I encountered with the "Squash and merge" functionality on GitHub. Despite selecting the "Squash and merge" option when merging a pull request, I observed that the merge was performed as a regular merge, retaining all individual commits from the feature branch in the main branch's history, rather than combining them into a single commit as expected.

Steps to Reproduce:

Create a new branch from the main branch.
Make multiple commits on the new branch.
Open a pull request to merge the new branch into the main branch.
Select the "Squash and merge" option and complete the merge.

Expected Behavior:

All commits from the feature branch should be squashed into a single commit in the main branch's history.

Actual Behavior:

All individual commits from the feature branch were retained in the main branch's history, indicating that a regular merge was performed instead of a squash merge.

I have verified that I have the necessary write permissions for the repository and that the repository is configured to allow squash merging, as outlined in the GitHub documentation
GitHub Docs
.

I would appreciate any assistance you can provide in resolving this issue.

Thank you for your attention to this matter.

Best regards,
Alex tsao

[Santas]

Multiple users from our org experienced the same bug.

[zeninsucks]

we are losing a lot of money because of this

[patrikholcak]

Related thread: https://github.com/orgs/community/discussions/153620

Official incident discussion https://github.com/orgs/community/discussions/153681

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐