We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
After the merge of #287, a developer will have the ability to provide custom configuration to Git Proxy.
To support developers in their use of Git Proxy, a breakdown of the configuration options would be helpful and is considered standard practice.
These configuration options can be added to the README.md, but also the newly created docs.
README.md
docs
The text was updated successfully, but these errors were encountered:
@coopernetes - happy to close this off with the existing Schema Reference that exists.
Agreed?
Sorry, something went wrong.
Yep, this is covered now as a reference page on the doc site.
Closing as completed in Schema Reference on documentation site 🎉
coopernetes
No branches or pull requests
After the merge of #287, a developer will have the ability to provide custom configuration to Git Proxy.
To support developers in their use of Git Proxy, a breakdown of the configuration options would be helpful and is considered standard practice.
These configuration options can be added to the
README.md
, but also the newly createddocs
.The text was updated successfully, but these errors were encountered: