79603865

Date: 2025-05-02 17:41:29
Score: 2.5
Natty:
Report link

When your pull request is merged, the original repo creates a new merge commit, which doesn't exist in your fork. That's why you're "1 commit behind." Even with no file changes, Git tracks the merge as a unique commit. This could technically cause a loop if both repos keep pulling and merging empty commits back and forth.

Reasons:
  • No code block (0.5):
  • Single line (0.5):
  • Starts with a question (0.5): When you
  • Low reputation (1):
Posted by: Udit Kumar