profile VS tokens

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:

Click on your profile in the top right corner > Settings > Developer settings, or visit: https://github.com/settings/tokens.

First of all, you need to generate a new GitHub Token. You can generate a token in your GitHub account settings at https://github.com/settings/tokens. Make sure to add the ‘read:packages’ scope to your token.

First, generate the GitHub token here.

Environment Variables Create a file .env in the root folder and add your own github api token as below

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

Versioning The initial step in this workflow involves generating version numbers based on git tag numbers. To access repository information, it's necessary to include a GitHub token in the secrets. You can create a GitHub token by following this link. Please keep in mind that secret names cannot start with the term GITHUB. For instance, you might save your GitHub token as TOKEN_GITHUB.

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.

Generate a classic PAT (personal access token) from Github with repo and admin:org scopes at least.

YOUR_TOKEN="no_token_for_you" # IMPORTANT: your Github API access key, make one at "https://github.com/settings/tokens"

You should click on that and then you will see Tokens (classic) which will bring you to https://github.com/settings/tokens