Problem
After migrating from GitLab to GitHub, CHANGELOG.md still references commit hashes as links pointing to gitlab.consulting.redhat.com. These links are inaccessible from the public GitHub repository and mislead contributors trying to trace changes.
Example from CHANGELOG.md:
([`7db166a`](https://gitlab.consulting.redhat.com/redhat-cop/openshift-virtualization-migration/openshift_virtualization_migration_ees/-/commit/7db166a...))
Proposed Solution
Update historical CHANGELOG.md commit links from gitlab.consulting.redhat.com/... to the equivalent GitHub URLs:
https://github.com/redhat-cop/openshift_virtualization_migration_ees/commit/<hash>
Going forward, ensure pyproject.toml is configured to generate GitHub-native commit links via python-semantic-release.
Files to Change
CHANGELOG.mdpyproject.toml (verify [tool.semantic_release.remote] section points to GitHub)
Problem
After migrating from GitLab to GitHub,
CHANGELOG.mdstill references commit hashes as links pointing togitlab.consulting.redhat.com. These links are inaccessible from the public GitHub repository and mislead contributors trying to trace changes.Example from CHANGELOG.md:
Proposed Solution
Update historical CHANGELOG.md commit links from
gitlab.consulting.redhat.com/...to the equivalent GitHub URLs:https://github.com/redhat-cop/openshift_virtualization_migration_ees/commit/<hash>Going forward, ensure
pyproject.tomlis configured to generate GitHub-native commit links viapython-semantic-release.Files to Change
CHANGELOG.mdpyproject.toml(verify[tool.semantic_release.remote]section points to GitHub)