-
Notifications
You must be signed in to change notification settings - Fork 27
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
generic fetcher: Add usage docs #718
base: main
Are you sure you want to change the base?
Conversation
/ok-to-test |
We also add a tiny introduction of each package manager here: https://github.com/containerbuildsystem/cachi2/blob/main/README.md#package-managers. We should have one for |
e5286c0
to
d8a3f6e
Compare
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.
This LGTM in the overall.
I think we should split the ADR to a separate commit, or even have it in a separate PR. The reason is that I think we'll merge the docs very quickly, but the ADR also implies making the package manager officially supported, so it'll bring a longer discussion (and we could use the same PR to also remove it from dev-package-managers
).
d8a3f6e
to
097a03d
Compare
This commit adds generic fetcher to the documentation as an experimental package manager, with instructions on usage. Signed-off-by: Jan Koscielniak <[email protected]>
097a03d
to
0c410e7
Compare
I have removed the ADR from this PR and will move it into a separate MR so docs can potentially be merged first. |
/ok-to-test |
Add documentation on how to use the generic fetcher and also an ADR to help move out of the experimental phase.
I've tried to follow the CONTRIBUTING.md guidelines, but since I did not see any previous ADR, I just tried to come up with something. Feel free to give more direction on how you want the docs to look like. Thanks!
Maintainers will complete the following section
Note: if the contribution is external (not from an organization member), the CI
pipeline will not run automatically. After verifying that the CI is safe to run:
/ok-to-test
(as is the standard for Pipelines as Code)