-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rework sample for dev hub #1
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work 🎉
From my side, everything looks fine (except a small typo) 👍
Please also add "topics" to the project description so it can be found easier 🙏 (guidelines are in notion).
Great to have the CI pipeline, with a smoke test as well 🙂
We might want to add the keepalive-workflow so the workflow will not go stale.
Also tagging @HarshCasper for the final approval 🙏
uses: actions/upload-artifact@v3 | ||
with: | ||
name: diagnose.json.gz | ||
path: ./diagnose.json.gz |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we haven't really decided yet on how we want to prevent the workflows from getting stale.
I started adding the keepalive-workflow action for the workflows where we test cloudpods, but I don't think we will be able those workflows to all samples in the first iteration.
Therefore, it might be a good idea to add the action in this main.yml
for the specific sample? WDYT @HarshCasper?
This PR adapts the sample to be ready for the developer hub, according to our standards. Work includes