Share your valuable feedback, comments or suggestions on Image Hosting GitHub

Image Hosting GitHub

Image Hosting GitHub

Github is nothing more than a tool to upload images or for hosting images. Within GitHub, there are few files which you need to use when you upload your images. Readme and wiki pages are few to mention.

(A) Uploading Images via Github: when an individual upload an image then he needs to add his image files with the repository by doing this, he is asking GitHub to track alterations and commits for each asset in his repository.

In most cases an individual's CDN assets do not need to be controlled through version while Amazon CloudFront or Akamai offers amazing CDN solutions, such as approaches (a) physically separates his repository from uploaded images, and (b) becomes an upload and maintenance PITA when he has a trouble-free set of static assets.

So the crucial advice is:

An individual should not try to add his images to the repository itself and then use a reference to a raw path. Furthermore, he needs not to worry about deploying his static images and other file attachments. Github does not presently furnish asset-management equipment for developer's repositories. However, GitHub DOES have a hidden feature that can be used as a CDN for assets like images, attachments, etc. it’s known with the name of Issues feature.
Smart use of Issues makes it quite simple to uploaded files that are associated with an individual's repository, and these files are not a part of its alteration processes. If a person creates an Issue within his repository, then his can drag-n-drop files to the issue comment to automatically upload and attach static content to his repository.

Here are few steps which individual can employ:

Step 1: An individual need to click on Issues' tab first of all. Next, he needs to create an issue with a title appropriate in the context of his images.

Step 2: Afterward an individual needs to create a new issue. An individual needs to upload images that will be used in the README.md document, so he will create an issue title which can be something like Images for README. An individual needs to take care of the instructions on the bottom of the write tab. It is quite important. He can drag-n-drop one or more images onto the Leave, a Comment box, and those files will be instantly uploaded to the hidden GitHub asset manager.

Step 3: Next step starts after completion of image uploading. An individual should know to use uploading images or assets.
After he submits the new issue, he has been able to see a recently attached image or images rendered legitimately. And finally, he can copy the required URL with a right-click on the image or images.
An individual can add more images to an issue at any time. Best of all, these images can now be referenced in his README docs or the Wiki pages.

(B) Publishing Demos

It is absurdly easy to publish live demos on Github once an individual knows the way. These two hidden features (1) Upload Images and (2) Publish Demos allow an individual to create superbly, informative project releases rich with images and demos. An individual doesn't need to limit him and needs to remember that his demo could even be an HTML page with embedded Plunkr or JSFiddle or Flash examples.

GitHub is used by 24 million people regularly to collaborate and share code. It hosts 80 million source code repositories for software in languages like JavaScript, Python, and C++.