Find GitHub hosted repositories that are updated by SVN (Take 2) #1582
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1582 +/- ##
============================================
- Coverage 35.14% 35.14% -0.01%
+ Complexity 17678 17677 -1
============================================
Files 1068 1068
Lines 163872 163894 +22
Branches 35013 35020 +7
============================================
Hits 57595 57595
- Misses 96717 96739 +22
Partials 9560 9560
Continue to review full report at Codecov.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new command "checksvngit" that scans the local SVN directory for repositories that are hosted on GitHub. These repositories will not updated after January 2024.
Test code for this is deliberately not included because this could be removed from the codebase circa January 2024 as being no longer necessary, The complexity of mocking a repository seems like it is more effort than it is worth especially when "testing the test" might be appropriate. Checking out a repository from GitHub is feasible but if the test checks out the repository via SVN the test will fail in January 2024. If it is checked out via git then the test setup will still have to provide information that would be created by SVN.
See #1580 for some discussion that lead to this approach.
Sample Output
Local installation of coandco-mafia-NewYou-trunk uses SVN to update from GitHub.
Local installation of Ezandora-Choice-Override-branches-Release uses SVN to update from GitHub.
Local installation of Ezandora-Comb-Beach-trunk-Release uses SVN to update from GitHub.
Local installation of Ezandora-FantasyRealm-branches-Release uses SVN to update from GitHub.
Local installation of Ezandora-Gain-branches-Release uses SVN to update from GitHub.
Local installation of Ezandora-PirateRealm-trunk-Release uses SVN to update from GitHub.
Local installation of Ezandora-Voting-Booth-trunk-Release uses SVN to update from GitHub.
Local installation of gausie-excavator-trunk-RELEASE uses SVN to update from GitHub.
Local installation of matt-chugg-manuel_progress.git-trunk uses SVN to update from GitHub.
Local installation of phulin-shorts-ui-branches-master-build uses SVN to update from GitHub.
Local SVN repos scanned for possible GitHub access via SVN.