Should one button do 2 actions (GitHub Case Study)?
Case in point - GitHub's "Fork" button. This button used to show all the forks that exist for the current repository but now it doesn't do that anymore. GitHub suddenly changed it to act as if the "user wants to create a new fork" so it open a new webpage asking you to create a new fork. This not only broke the old user experience but also made viewing the current forks almost impossible.
As a UX pro, how would you fix this button's behavior if the requirement was to :
- Show existing forks aka don't break old behavior
- Allow users to create a new fork
Should you make one button do 2 things like the 2 options can show up on the new page or when you press on button etc or is there a better way?
