Skip to content
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

chore(docs): document how to package and publicly release plugins #848

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

j-lanson
Copy link
Collaborator

@j-lanson j-lanson commented Jan 29, 2025

Resolves #849 .

Copy link
Collaborator

@alilleybrinker alilleybrinker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of minor changes, otherwise LGTM!

site/content/docs/guide/making-plugins/release.md Outdated Show resolved Hide resolved
site/content/docs/guide/making-plugins/release.md Outdated Show resolved Hide resolved
@j-lanson j-lanson force-pushed the jlanson/distribute-docs branch from 1b3f6bf to 445806e Compare January 29, 2025 16:42
@alilleybrinker alilleybrinker force-pushed the jlanson/distribute-docs branch from 445806e to fbb4d17 Compare January 29, 2025 19:01
@alilleybrinker alilleybrinker merged commit 57f7e15 into main Jan 29, 2025
8 checks passed
Copy link
Contributor

@ninaagrawal ninaagrawal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, just a couple of minor clarifications/grammar errors.

What is the purpose of lines 26-29. They look like broken links but I'm not sure if this is intentional


To start the packaging process, create a directory that contains your plugin
artifacts. Inside that directory you must write a [plugin manifest file](#the-plugin-manifest-file)
named `plugin.kdl` that tells Hipcheck how to run it. After you have written
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"it" could be more specific. I'm assuming it refers to the plugin artifacts

By now you should have a directory somewhere on your machine containing your
plugin manifest file and all of the artifacts for your plugin. Assuming your
plugin manifest has an entry in `entrypoint` that matches your current
architecture, you can run the plugin in a Hipcheck analysis. If built your
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If built should be changed to if you built

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Status: Done
Development

Successfully merging this pull request may close these issues.

How to distribute a plugin
3 participants