Deprecating JSON-formatted pipeline test configs in favor of YAML-formatted ones #139
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
7 tasks
💚 Build Succeeded
Expand to view the summary
Build stats
Trends 🧪 |
mtojek
approved these changes
Feb 22, 2021
2 tasks
rw-access
pushed a commit
to rw-access/package-spec
that referenced
this pull request
Mar 23, 2021
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.
What does this PR do?
This PR deprecates the JSON-formatted (
*.json) pipeline test configuration files in favor of YAML-formatted (*.yml) ones.Why is it important?
To bring consistency, since all other package configuration / metadata files are formatted as YAML.
Checklist
test/packagesthat prove my change is effective.versions/N/changelog.yml.Related issues