Closed carlreid closed 3 years ago
Just to be clear, I used an index.md. Might be better to use a markdown file if you want it "README" like, though I think a html file will be fine.
But otherwise yes, it should just work fine. You can check the action run and such on my fork. Nothing else needs to be changed 😊
Sure! Indeed, it would be preferable to use markdown, and we will populate it and make it look nicer :)
I'll change this and merge the PR!
Thanks again! 🎉 🎉 🎉
Bors merge
Timed out.
Bors merge
Build succeeded:
@eskombro Seems to be working great, also good job on the better looking index.md
😄 Thanks for reviewing so quickly 👍
Hello @carlreid! Thanks a lot for your PR!! 👍 Do you have a Twitter account? We really would like to highlight your work with the MeiliSearch account! 😄
@curquiza Sure would be an honor, I have @carl__reid though as you can see, I'm not so active 😆 Otherwise feel free to tag my GitHub profile 👍
@eskombro Seems to be working great, also good job on the better looking
index.md
😄 Thanks for reviewing so quickly 👍
Great, I was surprised with the timeout for merging, but seems to be a Bors problem. I just tested everything and works perfectly! Thanks 🚀
This workflow makes use of the helm/chart-releaser-action which will automatically create a git tag whenever the the chart
version
changes.This will cause a release to be deployed under your releases with a referenced
tgz
of the chart (example). After that, the action will create/update and index.yaml on thegh-pages
branch (example) and allow people to usehelm repo add meilisearch https://meilisearch.github.io/meilisearch-kubernetes
Note: You'll want to create a
gh-pages
branch first before merging this. You can create an empty branch like this:git checkout --orphan gh-pages
git rm -rf .
I also created an
index.md
(example) which you could use to add some instructions. Here's what it could like.Once you push the new branch, then modify the repo settings to be like:
Then all should be good 🙈
Resolves #13