awslabs / awslabs/Legacy-Code-Migration-Pipeline
Integrate Git
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Project prep (phase 0):
- set up local git repo
- provide option to connect to remote
Analysis, migration phase
- (BEFORE work on phase starts): pull from git
- (AFTER work on each phase ends): Push with message "Phase X, WP Y done"
(Business spec, test spec, implementation guide), Code implementation phase:
Provide instructions before and after each workpackage to:
- (BEFORE work on workpackage starts): pull from git
- (AFTER work on each workpackage ends): Push with message "Phase X, WP Y done"
Contributor guide
Research direction
Start by mapping the project's phase and workpackage workflow, since no files or tests are identified. Review how local repository setup, remote connection, pull steps, and push messages should fit before and after each phase; done means these instructions and options are defined for the full workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100