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

[FEATURE]-Automate-Initial-Plugin-Creation #18

Open
TrevorPayne opened this issue Jul 15, 2022 · 1 comment
Open

[FEATURE]-Automate-Initial-Plugin-Creation #18

TrevorPayne opened this issue Jul 15, 2022 · 1 comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed workflow

Comments

@TrevorPayne
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Individuals often go long periods of time before generating a new plugin. In some of that plugin development drought, it would become possible for either the actions required to change a template to be modified, or the developer simply doesn't know the process, or doesn't realize a process exists. In absence of documentation, which isn't always up to date, we should be able to script the initial solution generation process.

Describe the solution you'd like
A combination of locally-available powershell scripts and/or build actions to modify a recently-cloned solution file to adhere to internal naming conventions while being descriptive of the solution presented, along with automatically generating or editing a properly-formatted, internally-compliant nuspec file for nuget publishing.

Describe alternatives you've considered
The current solutions are entirely manual and frought with the possibility of human error or simple forgetfulness

Additional context
This isn't highly urgent, but I want to open a discussion about this. I strongly encourage you to share your thoughts on this issue.

@TrevorPayne TrevorPayne added enhancement New feature or request documentation Improvements or additions to documentation help wanted Extra attention is needed workflow labels Jul 15, 2022
@jonnyarndt
Copy link

jonnyarndt commented Jul 15, 2022

TP, thanks for chatting with me about this one. I agree, it would be very handy to have a bot/action/script that removes items from the EPI template that I don't need. Additional thoughts below:

  1. Are we assuming a recent-cloned solution is always the right base to start from every time (will it always include base features, base readme, all possible control methods, sudo code examples for bridging, with nothing removed)? Seems like I've seen multiple EPI's created with the majority of the base EPI template ripped out for what isn't needed (and I see nothing wrong with that).

  2. I like the single existing EPI template to clone from (then use bot/action/script to remove what we don't need). I like the idea of continuing to keep the single EPI template updated with standard practice, helpful TO-DOs, all possible control methods, and sudo code examples. If we start pulling from multiple base EPI locations or multiple EPIs, doesn't that complicate things?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request help wanted Extra attention is needed workflow
Projects
None yet
Development

No branches or pull requests

2 participants