You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently using the authored date for commit ingestion (so that's what is stored in the DB), but the commit date for searching. An example is the commit 45f31c9027782db69c6b76c5a04a1e833437891c in the backlot repo -- it will show as '6 hours ago' in the saved search but '4 days ago' in the commit view (as of writing this commit).
We definitely need to use the commit date for searching (otherwise newly pushed commits won't appear at the top of the list), so my vote is that we use commit date everywhere or store both dates and display them both in the commit metadata section.
We also need to think about how we will fix production data in either case.
The text was updated successfully, but these errors were encountered:
We are currently using the authored date for commit ingestion (so that's what is stored in the DB), but the commit date for searching. An example is the commit 45f31c9027782db69c6b76c5a04a1e833437891c in the backlot repo -- it will show as '6 hours ago' in the saved search but '4 days ago' in the commit view (as of writing this commit).
We definitely need to use the commit date for searching (otherwise newly pushed commits won't appear at the top of the list), so my vote is that we use commit date everywhere or store both dates and display them both in the commit metadata section.
We also need to think about how we will fix production data in either case.
The text was updated successfully, but these errors were encountered: