kykrueger commented on PR #1806: URL: https://github.com/apache/systemds/pull/1806#issuecomment-1519052864
It turns out that adding a custom status badge to the readme is a bit annoying since it needs to be saved somewhere, we have a few options: 1. Commit the status badge after the tests are successful. This creates some issues around the nature of open source projects, where you will have lots of branches coming from outside and the contributors will have to give the workflow permissions to commit to their branch. You will also need to give the workflows permission to commit inside of the github project. This also opens up a bit of a vulnerability for unintentional changes + a noisy commit history unless you switch to squash merging. 2. Host the status badge in some sort of cloud storage, and only let your workflows update it. Someone will need to provide an object storage account and add a secret in your github workflows, I can't do that myself from outside the project. This would also only work to display the most recent badge of main (could be misleading for forks). Someone had a neat solution of using gists to do this for free: https://discuss.circleci.com/t/how-to-show-badge-from-artifacts-in-github-readme/42109/2 3. I looked at storing the badges as artifacts, but there does not seem to be a static URL that we can use to fetch the latest badge from the main branch. I'd suggest going with option 2 despite the misleading badge in forks -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@systemds.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
