BigW Consortium Gitlab
- Previously, we sorted commits by date, which seemed to work okay. - The one edge case where this failed was when multiple commits have the same commit date (for example: when a range of commits are cherry picked with a single command, they all have the same commit date [and different author dates]). - Commits with the same commit date would be sorted arbitrarily, and usually break the network graph. - This commit solves the problem by both sorting by date, and by sorting topographically (parents aren't displayed until all their children are displayed) - Include review comments from @adamniedzielski A more detailed explanation is present here: https://gitlab.com/gitlab-org/gitlab-ce/issues/30973#note_28706230
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
api/helpers | Loading commit data... | |
banzai | Loading commit data... | |
bitbucket | Loading commit data... | |
ci | Loading commit data... | |
constraints | Loading commit data... | |
container_registry | Loading commit data... | |
gitlab | Loading commit data... | |
json_web_token | Loading commit data... | |
mattermost | Loading commit data... | |
microsoft_teams | Loading commit data... | |
additional_email_headers_interceptor_spec.rb | Loading commit data... | |
disable_email_interceptor_spec.rb | Loading commit data... | |
event_filter_spec.rb | Loading commit data... | |
expand_variables_spec.rb | Loading commit data... | |
extracts_path_spec.rb | Loading commit data... | |
file_size_validator_spec.rb | Loading commit data... | |
gitlab_spec.rb | Loading commit data... | |
repository_cache_spec.rb | Loading commit data... |