19
#NCUG
Important Message !!!
• If you are still have your content on github.ibm.com it needs migrating to github.com
• There is a procedure
• Migration Process
• Make sure to have a local fork or archive of the existing repository you wish to preserve and use.
• Create an account at https://github.com if you do not already have one.
• Create a new repository at github.com into which you can migrate the existing customization files, taking note of the guidance below:
• iYou cannot re-use the exact same repository name because Customizer builds an aggregated store of all customizations from both
github.ibm.com and github.com and repository names must be unique.
• There is no need to continue using the organization ID as the repository name.
• Use a meaningful name for your repository. Please avoid using 'customizer' or 'customization' in the name if possible. Adhere to the github
naming convention by using all lowercase letters with hyphens as separators (e.g bluemix-weather-widget, uniqueName-samples). You
can rename your repository in the repository Settings tab - see Settings - Option - Repository Name - Rename.
• Please include a readme file explaining the repository contents and its intended purpose, even if this is very brief and high level.
• You can optionally include a licence. Ideally we hope your project will graduate to something that others would like to consume or maybe
even help extend. If you add a license to your project we recommend the Apache License 2.0.
• 4. Copy the files from the existing fork or archive into the new repository.
• 5. Invite the
[email protected] account into the new repository so that it can fork and merge from your new repository into the organization
from which Customizer builds the customizations.
• 6. Notify the Customizer Development Team via email at
[email protected] when ready for content to be pulled into the Customizer
organization in GitHub.
• 7. Once the changes have been merged from the new repository, update the application definition JSON to reference the new repository name.
• 8. Test that the customizations are functioning correctly.