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

Plugin Author-Editable Description, Release Notes and Hashtags #18

Open
lingocoder opened this issue Nov 27, 2019 · 0 comments
Open

Plugin Author-Editable Description, Release Notes and Hashtags #18

lingocoder opened this issue Nov 27, 2019 · 0 comments

Comments

@lingocoder
Copy link

Please can we make changes to our own plugin descriptions, release notes and tags?

Expected Behavior

I specify a description and tags in the pluginBundle{} block of the build script that I use to publish my plugin. I expect for the description and tags to be displayed on the plugin portal pages exactly as I specify them in the build script.

Current Behavior

The description and tags that I specify in the pluginBundle{} block of the build script that I use to publish my plugin, are ignored by the rendering process of the plugin portal.

The text that I specify in the build script does not get displayed. I therefore need to request that someone on the Gradle team manually make the changes I require on my behalf.

Context

As a plugin developer, I am continually adding features and making other changes to my plugin.

Typically, the textual descriptions of the new features also need to be updated accordingly. Likewise for the hashtags — which prospective users might use as metadata keywords on which to search for plugins that provide the capabilities they're looking for.

It would help users find plugins that meet their needs quicker if the descriptions, tags and other metadata that describes plugins are all updated the instant the latest version of the plugin is published to the plugin portal.

Having some kind of mechanism that allows plugin authors to update their own description and tags themselves would be super valuable to end-users and plugin authors.

Such a feature would be valuable for the Gradle team too, since I imagine manually updating static web page content is not the most efficient use of your time either.

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

No branches or pull requests

1 participant