- Rename GitHub repository
- Determine public vs. private API surface in order to get a clear picture on what code elements can be renamed without triggering a breaking change and therefore a major release (if using semantic versioning)
- Update source code references
- Classes
- Interfaces
- Imports
- Do keep in mind that these have to be separated based on internal vs. published API elements
- Update source code references
- Update links pointing to the GitHub repository within
- source code
- documentation that's managed separately from the source code (if applicable)
- ReadTheDocs page (if applicable)
- Mailing list
- Chat rooms (Discord)
- Calendar meetings (where applicable)
- Wiki pages
- Project page update on Hyperledger site
- Package managers/published artifacts (where applicable)
- npm
- Maven/Gradle
- Container images
- Slide decks (if applicable)
- Whitepapers (if applicable)
- GitHub Integrations (where applicable):
- ZenHub
- MergeFreeze
- Jira
- Gitter
- GitGuardian
- etc.
Manage space
Manage content
Integrations