Provides a mechanism to "lock" a source GH repo (#2)

[pmartindev]

Issue #385

Added a flag to allow for archiving the source repository before migration. This will allow migration users to block any changes to their repositories that would normally not be included in the migration. Looking for any feedback and discussion on the issue.

• [X] Did you write/update appropriate tests
• [ ] Release notes updated (if appropriate)
• [X] Appropriate logging output
• [X] Issue linked
• [ ] Docs updated (or issue created)

[pmartindev]

cc: @tj-cappelletti @cvega

[github-actions[bot]]

Unit Test Results

480 tests   480 :heavy_check_mark:  30s :stopwatch:     1 suites      0 :zzz:     1 files        0 :x:

Results for commit e30c0725.

:recycle: This comment has been updated with latest results.

[dylan-smith]

I think this should be implemented as a separate lock-repo command to be consistent with the design already established in ado2gh lock-repo. There is an issue for this improvement with some guidance on design here: https://github.com/github/gh-gei/issues/385

[pmartindev]

Hey @dylan-smith, sorry I linked the wrong issue in the comment 😭 It's corrected now.

[github-actions[bot]]

Package	Line Rate	Branch Rate	Complexity	Health
gei	88%	84%	432	✔
ado2gh	89%	83%	541	✔
Octoshift	87%	76%	492	✔
Summary	88% (4526 / 5131)	82% (936 / 1147)	1465	✔

[robandpdx]

A better implementation would be to add the lock_repositories boolean to the StartMetadataArchiveGeneration function and use it in the options object there. Similar to skipRelease boolean. https://github.com/github/gh-gei/blob/main/src/Octoshift/GithubApi.cs#L461-L476

[dylan-smith]

Superseded by #589