Migration tool between servers

Open
#257 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api, backend-api-design

Research direction

No file or test is named. Start by reviewing the Python API client's existing user and project operations and how the API could support copying or moving them between Server A and Server B. Done means the supported scope and behavior are defined and implemented with verification for migration without requiring full history.

Written by the indexing model from the issue text.

Description

enhancement

I am not sure if it is feasible, but it will be good to extend the API to move/copy users and projects (even if not the full history) from Server A to Server B.

Dominant language
Python
Stars
23
Forks
12
Avg merge
2d 13h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/python-api-client

All issues in MerginMaps/python-api-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.