Add automatic updating of README #16
Open
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
rnc
commented
Jan 29, 2025
| <replacementType>file-contents</replacementType> | ||
| <fileMask>.md</fileMask> | ||
| <!-- Bit of hack as it is assuming this version is always 1.x --> | ||
| <findRegex><version>1.*</version></findRegex> |
There was a problem hiding this comment.
I'm not entirely happy with this but I think the only other way of doing it would be to remove any <version>[numeric]... from the readme that isn't for ide-config ; currently the only other instance is:
<artifactId>spotless-maven-plugin</artifactId>
<version>2.44.2</version>
Perhaps it would be better to move the above into a properties block so it simplifies the above regex? Thoughts?
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.
@thescouser89 Idea being that when a release is run, the code section in the README is automatically updated with the most recent released version of the configuration. I've 'semi-tested' this ; I can't run a full test without doing a release.