Task #3 Let's code privately
Problem
Recently, HTTPie, a popular open-source project hosted on GitHub took to their blog to notify it's users that the project has lost all it's "stars" on GitHub when one of the maintainers of the project mistakenly set the project's visibility to private. Before the incident, HTTPie had ~54,000 stars — or those many GitHub users who've bookmarked the repository. In recent years, the number of stars has become a proxy for how trusted the project is. Losing all the stars is a big blow to all the effort the maintainers of the project put in over the years.
In its current behavior, GitHub removes all the stars and watchers of a public, open-source repository when it's made private. This action is destructive and irreversible, and GitHub shows a confirmation dialog box in the UI before the user can take this action on a repository. However, as the maintainer of HTTPie argues, just a confirmation box isn't enough for an action that is as destructive as decimating the community built over years.
Assuming GitHub doesn't change its behavior of removing all the stars irreversibly when making a public repository private, your job is to redesign the UX when a user changes the status from a repository's settings view so a repository like HTTPie doesn't have to suffer an incident like this one.