Describe the bug
I was analyzing the Apache Maver Core repository (https://github.com/apache/maven). I wanted to only analyze from_commit = "388e659a17d23cba75afd93336181f768248efa3" till the latest commit. This from commit hash was made on 2010-09-26 But when I add this filter value to the Repository class, instead of starting from 388e659a17d23cba75afd93336181f768248efa3 it starts from f9dca87cad2671becaac63df47077bf8660b9d33 which was made on 2005-12-12. There are an extra 1286 commits between actual start and intended start.
To Reproduce
To reproduce this, the following steps can be followed -
- Clone the Apache Maven repository (https://github.com/apache/maven)
- Write a small script like below:
for idx,commit in enumerate(Repository(<path_to_cloned_repo>,
include_refs=False,include_remotes=True,
from_commit="388e659a17d23cba75afd93336181f768248efa3",
).traverse_commits()):
if commit.hash=="388e659a17d23cba75afd93336181f768248efa3":
print("ID",idx)
print(commit.committer_date)
if idx==0:
print("Oldest-",commit.hash)
print("Oldest-",commit.committer_date)
OS Version:
Windows/Linux
Describe the bug
I was analyzing the Apache Maver Core repository (https://github.com/apache/maven). I wanted to only analyze
from_commit = "388e659a17d23cba75afd93336181f768248efa3"till the latest commit. This from commit hash was made on 2010-09-26 But when I add this filter value to theRepositoryclass, instead of starting from388e659a17d23cba75afd93336181f768248efa3it starts fromf9dca87cad2671becaac63df47077bf8660b9d33which was made on 2005-12-12. There are an extra 1286 commits between actual start and intended start.To Reproduce
To reproduce this, the following steps can be followed -
OS Version:
Windows/Linux