fix(ci): make sure to generateUsage help files before triggering build #4
Conversation
This file contains hidden or 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
this makes sure that when README.md is updated with latest version number(s), there is also an up-to-date collection of usage help files available. This is required, because even when using a dependency to `generateUsage` task, the config phase of spotlessMarkdownApply has already picked up the empty/non-existing files, even though they would be available when the task is actually run... so by generating the files before hand, we make sure they are available in config phase of spotlessMarkdownApply.
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.
this makes sure that when README.md is updated with latest version number(s), there is also an up-to-date collection of usage help files available. This is required, because even when using a dependency to
generateUsagetask, the config phase of spotlessMarkdownApply has already picked up the empty/non-existing files, even though they would be available when the task is actually run...so by generating the files before hand, we make sure they are available in config phase of spotlessMarkdownApply.