Revoke Star behavior that cannot be applied to Archived repositories

[2659170494]

🏷️ Discussion Type

Product Feedback

Body

Hello, this is my first time trying Feedback here.
I don't know when this happened, but when I tried to star the archived repository just now,
I was told that I couldn't star it, the entire Star button is gray, and I can't even cancel it???

I understand that Github is making changes to anti fraud and advertising, and I have also noticed that stargazers and viewers are currently unable to view (including archived repositories).

But I can't understand what kind of problems an Archived repository's Star behavior can bring, I really hope it's just a simple bug.
If you check my Github profile, you will find that my Star count has exceeded 5k+,
And I rely heavily on this feature. Some repositories have Archive issues due to reasons such as Lspose and MS-DOS, but I don't want to forget about them,
The search function of Star is very suitable for me because it can not only search for warehouse names directly, but also search based on warehouse descriptions or tags.
I also don't want to directly add the repository page to my browser bookmark, because as long as you have used it, you will understand 😢

[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. ⭐

[ljcool2006]

I am experiencing the same problem that you have. A week ago I described the problem on a Reddit post where I found a workaround by searching the repo's name and starring it from there. I'm assuming it's an A/B test because there isn't anything on the GitHub documentation about it and it reverted back to the old behavior for a while before I got the new behavior again.

[2659170494]

I am experiencing the same problem that you have. A week ago I described the problem on a Reddit post where I found a workaround by searching the repo's name and starring it from there. I'm assuming it's an A/B test because there isn't anything on the GitHub documentation about it and it reverted back to the old behavior for a while before I got the new behavior again.

In addition to searching, the mobile client (Github for Android) can also perform Star operations normally.
The interception only occurred on the front-end. I used the rewriting content of devtool to change the "canStar" of "react app. embeddedData" to "true", and observed that everything was normal in the API.
But I asked some of my friends and they also encountered this situation, but since I know relatively few friends, I am not sure if this is not an A/B test.

And regarding stargazers and viewers, I did find these two Twitter posts, one of which has already proven that Github is removing this feature.
But until now (a month later), the API references corresponding to these two buttons still remain on the page, as stated in this tweet.
So, I suspect this isn't over yet; clearing out "/stargazers" was just the first step, and optimizing the "Star" feature itself might well be their next move 😔.
As for anything else, I can't think of any other possible explanation besides a bug.