point users to the matching version README on the plugins website url #63
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
|
Need to either close this or merge it in prior to the plugin moving to the jbake repo. |
|
It depends. If we follow trunk based development then yes, this needs updating. If we follow trunk releases (main is release, development is well, development) then there's no need. This depends on how the parent jbake repository will follow its development workflow. |
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.
Currently the website url on the plugin page points to the latest state of the repository main branch.
It can be confusing looking at the README which is not released yet.
Maybe it helps if the users are pointed directly to the latest release like https://github.com/jbake-org/jbake-gradle-plugin/tree/v5.4.0,
derived from the current plugin version.