Skip to content

Make inability to deal with 'first commits' more obvious in the docs #384

Closed as not planned
Task
Closed as not planned
Make inability to deal with 'first commits' more obvious in the docs#384
Task
Labels
help wanted

Description

@Byron
Byron
opened on Feb 14, 2016

GitPython cannot gracefully handle the following situations:

  • empty repository
  • diffing of the first commit against the (implied) empty tree

It would be nice to make this more obvious in the first steps of the documentation, possibly even in the README file.

This issues was spawned from #379.

Activity

  1. Byron
    added this to the milestone on Feb 14, 2016
  2. Byron
    added
    help wanted
    on Feb 14, 2016
  3. Byron
    modified the milestones: v2.0.0 - Features and Fixes, on Apr 24, 2016
  4. Byron
    modified the milestones: v2.0.3 - Bugfixes, v2.0.4 - Bugfixes on May 25, 2016
  5. nvie
    modified the milestones: v2.0.4 - Bugfixes, , v2.0.5 - Bugfixes on May 30, 2016

  6. 25 remaining items

  7. Byron
    modified the milestones: v2.1.1 - Bugfixes, v2.1.0 - better windows support on Oct 22, 2016
  8. Byron
    modified the milestones: v2.1.1 - Bugfixes, on Dec 8, 2016
  9. Byron
    modified the milestones: , on Mar 8, 2017
  10. Byron
    modified the milestones: v2.1.4 - Bugfixes, v2.1.8 - Bugfixes on Dec 11, 2017
  11. Byron
    added the
    Task
    issue type on Jul 20, 2026
  12. Byron
    closed this as not plannedon Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wanted

    Type

    Task

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions