chore: update links in preparation for repository move#7373
Conversation
|
@jeremylong you're still working on this, or is it only draft to prevent accidental merge as it needs to wait till just-before-move? There are still a significant amount of github URLs in the current branch in need of change to make the code properly reflect the new home after the move. Let me know if I can help on getting those updated. |
|
It was a draft for both reasons - I hadn't finished updating things (I ran out of time) and I'm keeping this as a draft until the move happens. As of now - I believe all of the references have been updated. If you know of anything I missed please speak up. |
|
@jeremylong I've processed most items in my PR towards the scratch-branch.... an item I wasn't sure about was the coverity config. I can imagine that the jeremylong/DependencyCheck there is a reference to a Coverity project and not a reference to the github project as such. If not I think there would be an additional change required in the coverity_scan.sh (the value for env variable COVERITY_SCAN_PROJECT_NAME) - however your update to coverity.yml appears to suggest the change would be needed as in there you've modified the project parameter various times |
To be merged just prior to transferring the repository.
See #7235