[
https://issues.apache.org/jira/browse/SLING-7684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522318#comment-16522318
]
Dan Klco commented on SLING-7684:
---------------------------------
[~bdelacretaz] Strange, it seems like this is something GitHub is doing:
[https://help.github.com/articles/about-anonymized-image-urls/]
If you look at the raw README.md file it has the direct link to the SVG on the
Sling website:
[https://raw.githubusercontent.com/apache/sling-org-apache-sling-launchpad-integration-tests/master/README.md]
It *seems* like if we set no-cache headers this will force GitHub to use our
images, but this will also have the unfortunate side effect of disabling
caching on static images:
[https://github.com/github/markup/issues/224
]
[https://help.github.com/articles/about-anonymized-image-urls/#an-image-that-changed-recently-is-not-updating]
So I guess the question is, is it sufficient to have the images correct in the
README or do we need them to also be present in the HTML of the readme pages?
> Add Badges to GitHub Repo Readmes
> ---------------------------------
>
> Key: SLING-7684
> URL: https://issues.apache.org/jira/browse/SLING-7684
> Project: Sling
> Issue Type: Task
> Reporter: Dan Klco
> Assignee: Dan Klco
> Priority: Minor
> Attachments: Sling-Repos.csv, features-page.png, modules-page.png,
> project-readme.png, readrepo.sh
>
>
> Add badges to the README.md files in all of the GitHub repositories
> indicating important status items, links to other resources and other good
> information. Currently looking into:
> *Static Badges*
> * Contrib
> * Deprecated
> * Testing(?)
> * Tooling(?)
> * License
> *Dynamic Badges*
> * Build Status
> * Tests
> * Maven Central
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
