LemePush

Documentation

Complete guide to repository history management

Getting Started
Essential steps for repository history rewriting

1. Repository Preparation

Ensure you have the following prepared before beginning:

  • Source repository URL with the history you wish to modify
  • Destination repository URL (empty or prepared for overwriting)
  • GitHub credentials with appropriate access permissions

2. Configuration

Complete the form with your specific requirements:

  • Repository URLs (source and destination)
  • GitHub username for authentication and tracking
  • Commit date preferences (original or custom range)
  • Optional contributor information

3. Processing

Initiate the process by clicking "Rewrite History." The system will display real-time progress updates during processing. Processing time varies based on repository size and complexity.

4. Implementation

After successful processing:

  • Download the generated ZIP file
  • Extract contents to your local environment
  • Follow the included README_PUSH.md instructions
  • Verify the changes in your destination repository
Form Field Reference
Detailed specifications for repository configuration

Repository Configuration

Essential repository location parameters

Source Repository URL

The complete URL of the repository containing the history to be rewritten. Must be in the formathttps://github.com/username/repository.git

Destination Repository URL

The target repository URL where the modified history will be pushed. Should be an empty repository or one prepared for complete overwriting.

Authentication

User identification parameters

GitHub Username

Your GitHub username is required for job tracking, session management, and proper commit attribution in the rewritten history. Ensures secure processing and accurate notifications.

Commit Timeline Configuration

Parameters controlling commit chronology

Original Date Preservation

Toggle to maintain original commit timestamps from the source repository. When enabled, the exact chronological sequence of development is preserved. When disabled, commits will be redistributed according to your custom date range.

Custom Date Range

Available when original date preservation is disabled. Define the temporal boundaries for commit redistribution:

  • Start Date: The earliest timestamp in the rewritten history
  • End Date: The latest timestamp in the rewritten history

The system proportionally redistributes commits across this timeframe while maintaining their sequential integrity.

Contributor Management

Optional attribution configuration

Optionally specify additional GitHub usernames to include in the commit history attribution:

  • Add contributors by entering GitHub usernames in the provided fields
  • Manage multiple contributors using the add/remove controls
  • Commits will be distributed among specified contributors to create a collaborative history

This feature is particularly useful for demonstrating team development patterns or establishing contribution records.

Processing Indicators

Real-time status monitoring

After submission, the system provides comprehensive progress monitoring:

  • Progress Bar: Visual representation of completion percentage
  • Status Messages: Textual updates on current processing phase

The system employs real-time communication via WebSockets (Pusher) when available, with automatic fallback to polling for consistent status updates.

Results & Delivery

Process completion and artifact retrieval

Upon successful completion, the system provides:

  • Confirmation Message: Verification of successful processing
  • Download Link: Access to the compressed repository with rewritten history
  • Implementation Instructions: Guidelines for deploying the modified repository

In case of processing errors, detailed diagnostic information and potential remediation steps are provided.