-
Notifications
You must be signed in to change notification settings - Fork 14
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
Improve documentation (provisioners, testsuite) #139
Labels
Milestone
Comments
dosubot
bot
added
the
stale
Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
label
Sep 19, 2024
dosubot
bot
removed
the
stale
Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
label
Oct 19, 2024
github-project-automation
bot
moved this from In Progress
to Done
in Intersmash library
Oct 19, 2024
Hi, @fabiobrz. I'm Dosu, and I'm helping the intersmash team manage their backlog. I'm marking this issue as stale. Issue Summary:
Next Steps:
Thank you for your understanding and contribution! |
dosubot
bot
added
the
stale
Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
label
Jan 20, 2025
fabiobrz
removed
the
stale
Issue has not had recent activity or appears to be solved. Stale issues will be automatically closed
label
Jan 21, 2025
This can now be closed as resolved, given the latest improvements to the the project documentation, and the final refinement in #224 |
github-project-automation
bot
moved this from In Progress
to Done
in Intersmash library
Jan 22, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The provisioners documentation should quickly drive the user to selecting the right tool for their use, so e.g.: a simple table of available (grouped) provisioners per service/product, along with a one-liner usage hint, would help.
The testsuite documentation shuld explain the available profiles and deployments build options.
The text was updated successfully, but these errors were encountered: