-
Notifications
You must be signed in to change notification settings - Fork 28
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
Document configuration options #369
Comments
I created a PR in a temp repository: jsmrcka/quarkus-test-framework-wiki#1. @michalvavrik It contains proposed changes which document missing config options. I am not aware of a way how to make PR into a wiki, so this is a workaround. After a review, I can push identical changes directly into the TF wiki. |
Sounds good @jsmrcka . |
No PRs into wiki, just direct edits, but I like to have external view for the planned changes as in jsmrcka/quarkus-test-framework-wiki#1. +1 |
I don't agree, PR was needed, direct edit is not a good way @rsvoboda . I made several comments, some of them might be good :-) |
I checked, @jsmrcka must grant you access, I don't have rights. |
I mean PR as a way to collaborate, yeah, there is no way to make PR for Wiki AFAICT |
Changes from the PR jsmrcka/quarkus-test-framework-wiki#1 have been pushed to the wiki main. I'm leaving this issue open, as the automation options are still TODO. |
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
@fedinskiy has this in progress so assigning him |
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Since all of them are now gathered in one place it would become easier to monitor and document them Required for potential automation of quarkus-qe#369
Document configuration options
E.g. " ts.global.delete.folder.on.exit=false" is not documented
Look at automation options
The text was updated successfully, but these errors were encountered: