ginjaninja 631 Posted July 11 Posted July 11 (edited) Purpose: I was finding it longwinded creating a new plugin shell at the beginning of a project. I created this repository with an automated workflow to quickly instantiate a working plugin inside a git repository framework. https://github.com/ginjaninja1/EmbyTemplatev2 Hopefully others might find a use, I'm hoping its going to make it quicker to startup new plugins. Zero-Configuration Scaffolding: Uses automated GitHub Actions to rename namespaces, solution files, and projects instantly upon repository creation. .gitignore prepopulated: To ensure obj, bin and .vs folders are excluded from repository setup.bat: instantiates a pre-commit in .git/hooks/ so any commit with "[bump]" at the END of description increases the the version number in .csproj. Working Plugin with thumbnail: Ready to compile plugin with thumbnail, pluginui configuration page with autopostback (autosave) and task. launchSettings.json: Ready to launch Emby with breakpoints for debugging Post Build Event: Ready to copy compiled code to Emby plugins folder in current users %appdata%. Supress dependency file: No value in copying this into plugins folder. Further instruction/guidance in readme.md in repository. Issues and suggestions welcome. Disclaimer: Vibecoded with Claude. The sample code will 'do work' if you schedule / run the task so avoid doing that 'blind'. Edited 1 hour ago by ginjaninja
ginjaninja 631 Posted 1 hour ago Author Posted 1 hour ago added a guid generation workflow event for plugin.cs
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now