Make publish workflow automatically parse plugin name #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…viding one in workflow
quest |
JustArchi
approved these changes
Mar 12, 2024
JustArchi
added
the
✨ Enhancement
|
Good addition, thanks 🏆 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull re
My suggesting is to parse plugin name from
Directory.Build.propsinstead of providing one in a workflow text itself. This way all actions in this template will be plugin name-independent, which will, in turn, allow users to easily update those actions from the template repo (even automatically, if needed), thus benefiting from latest changes added there.