societe-generale / societe-generale/github-crawler

lastUpdateDate doesn't match last commit date for repo/branch

Open
#42 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Kotlin
Stars
111
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Summary

The lastUpdateDate gives last update date of any branch for a repo. Generally either it should give the last commit date on that branch or there should be a new field called lastCommitDate for every branch.

Type of Issue

It is a :

  • bug
  • request
  • question regarding the documentation

Motivation

job should complete and return a field for last commit date on branch.

Current Behavior

Currently all the branches for a repo are having same value for lastUpdateDate.

Expected Behavior

lastUpdateDate should be different for each branches of Repo Or there should be a new field which can represent last commit date on the branch.

Steps to Reproduce (for bugs)

When we run the crawler with crawlAllBranches config as true, we can check same lastUpdateDate for all branches for a repo.

Your Environment

  • Version used: 1.0.6
  • OS and version: Linux
  • Version of libs used:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the crawler path used when crawlAllBranches is true and locate where lastUpdateDate is computed for repository branches. Reproduce the issue with multiple branches, then verify that each branch reports its own last commit date or that the agreed separate field is returned.

Written by the indexing model from the issue text.

Assessment

Tech stack
kotlin
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.