Cleanup Before First Release

[nrayburn-tech]

• Update the pluginGroup in gradle.properties, the plugin id in plugin.xml, and the kotlin packages
• Add a plugin icon to plugin.xml Update the plugin icon #68
• Update the vendor in plugin.xml fix: Update plugin vendor #69
• Cleanup the README.md chore: Readme updates #70
• Update Github secrets with the required tokens to publish
  • Set the Plugin Signing related secrets
  • Set the Deployment Token
• Remove original template code that isn't used by the plugin Cleanup unused code #56
• Update changelog chore: Update changelog #79
• Review the Legal Agreements.
• Config file support Oxlint configuration file setting #84.

Last step is to Publish a plugin manually for the first time.

[nrayburn-tech]

@IWANABETHATGUY I think you or somebody else on the project will need to handle the Github secrets, review the legal agreement (I think this is just an FYI, no action is required), and once everything else is done publishing the plugin manually.

[InSyncWithFoo]

You might want to pick a better ID here (and don't forget to change the URL), given that this repository is now placed under @oxc-project:

pluginGroup = com.github.iwanabethatguy.oxcintellijplugin
pluginName = oxc-intellij-plugin
pluginRepositoryUrl = https://github.com/IWANABETHATGUY/oxc-intellij-plugin

pluginGroup is the ID used to uniquely identify a plugin, whereas pluginName is the user-facing name. The latter should be in Title Case and does not contain intellij (or jetbrains, webstorm, etc.). More information can be found in this guide.

[IWANABETHATGUY]

You might want to pick a better ID here (and don't forget to change the URL), given that this repository is now placed under @oxc-project:

pluginGroup = com.github.iwanabethatguy.oxcintellijplugin
pluginName = oxc-intellij-plugin
pluginRepositoryUrl = https://github.com/IWANABETHATGUY/oxc-intellij-plugin

pluginGroup is the ID used to uniquely identify a plugin, whereas pluginName is the user-facing name. The latter should be in Title Case and does not contain intellij (or jetbrains, webstorm, etc.). More information can be found in this guide.

Yeah, we already discuss here #66 (comment)

[nrayburn-tech]

Anything else to include in a first release besides the existing list in the issue? Working on the changelog updates now. I'll keep working on features when I can, but I wasn't sure if there was anything else necessary for a first release.

[IWANABETHATGUY]

I think it looks good for now, let me add a secret and try to make the release workflow work

[IWANABETHATGUY]

Thanks for your work again

[nrayburn-tech]

I think you have to do a manual release for the first one. It looks like there might be some manual parts involved Publish a plugin manually.

[nrayburn-tech]

Should probably implement #84 before a release, but other than that I’m not aware of any blockers for a first release.

[IWANABETHATGUY]

Should probably implement #84 before a release, but other than that I’m not aware of any blockers for a first release.

Ok, let's wait for the nested configuration to land and then push forward.

[simonbuchan]

I just went through the process for a manual plugin release (having missed this, dammit) - you can specify a channel like preview so it doesn't get marked as a stable release and, as far as I can tell, not recommended in the plugins search.

The page is here, still under moderation review, so let me know if it shows up and confuses people and I'll take it down or whatever: https://plugins.jetbrains.com/plugin/25948-oxlint

---

Here's the docs on it: https://plugins.jetbrains.com/docs/marketplace/custom-release-channels.html

Notably:

When using a non-default release channel, users will need to add a new custom plugin repository to install your plugin.