Recover git history #2

Open
opened 2023-11-27 11:50:45 +00:00 by slamora · 1 comment
Collaborator

While migrating code to this repository, the previous git history has been lost.
We are working to rebuild current commits on top of the previous git history to recover it.

This issue is just for documenting the process if in the future could be useful.

While migrating code to this repository, the previous git history has been lost. We are working to rebuild current commits on top of the previous git history to recover it. This issue is just for documenting the process if in the future could be useful.
Author
Collaborator

Reference to some orphan commits (they are included on "the big commit" 53fa5a02). Both are related to upgrade code to be compatible with newer Django versions:

Reference to some orphan commits (they are included on "the big commit" [53fa5a02](https://gitea.pangea.org/pangea/django-orchestra/commit/53fa5a02eb08c39128812a5c29a050a08a098d43)). Both are related to upgrade code to be compatible with newer Django versions: - [Django 3.1](https://gitea.pangea.org/attachments/f7af7640-80ec-476c-90ea-993a2aa29bbe) - [Djaango 4.0](https://gitea.pangea.org/attachments/dc71cae0-9865-46f3-97b4-0d812086c5fa)
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: pangea/django-orchestra#2
No description provided.