Skip to content
Discussion options

You must be logged in to vote

@aungzayyanaing Thank you again for suggesting the temporary default-branch switch. I tested it across multiple affected repositories, and it worked repeatedly. I also completed a new authenticated GraphQL audit to verify the recovery.

Exact procedure I used

  1. Create a temporary branch (tmp-contribution-test) from the existing default branch, pointing to the same commit.
  2. In Settings → General → Default branch, set the temporary branch as default.
  3. Immediately switch the default branch back to the original one (main in my repositories). There was no need to visit the repository homepage between changes.
  4. Delete the temporary branch.
  5. Refresh the GitHub profile and check the missing historical …

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies

This comment was marked as low quality.

@Blackpachamame
Comment options

Answer selected by queenofcorgis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Repositories The core of version-controlled code storage Welcome 🎉 Used to greet and highlight first-time discussion participants. Welcome to the community! source:ui Discussions created via Community GitHub templates
2 participants