profile VS git-privacy

So, have your GitHub registration properly filled out. That way you don't need to make any code changes. 🤖

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

That account has the "Make profile private and hide activity" option turned on in https://github.com/settings/profile which hides your contributions, activity, followers, followings, stars, etc.

Abra o GitHub, e vá para Settings,

Go to your settings at https://github.com/settings/profile and check "Include private contributions on my profile"

By opting to allow developers to use their own accounts to sign in, with or without SAML SSO, developers are able to stay in control of their own GitHub identity. They also don’t have to manage a separate “work” GitHub account and can keep data such as commit statistics all in one place. To see it in action, go to https://github.com/settings/profile and enable the checkbox as seen in the screenshot below:

So, have your GitHub registration properly filled out. That way you don't need to make any code changes. 🤖

I just get 500 on the homepage, and my profile also 500s when logged out. Most other things still seem to work, including https://github.com/settings/profile where I could turn it off.

To create the GitHub Client ID and Client Secret, go to https://github.com/settings/profile, Developer Settings on the left-hand nav-bar, OAuth Apps, New OAuth App. Fill in a name and your localhost with port for the homepage URL. Copy the homepage URL and add /api/auth/callback/github. This will allow the /api/auth/[...nextauth].ts file to catch this callback URL and use it to create a user in the database. The form should look something like this:

There is also git-privacy[1] for rounding all of your commit timestamps to the hour or day.

[1]: https://github.com/EMPRI-DEVOPS/git-privacy