Extend the api guidelines with a concrete ruleset.#7
Open
ravindrapalaskar17 wants to merge 672 commits intoExtend-the-API-guidelines-with-a-concrete-rulesetfrom
Open
Conversation
🦙 MegaLinter status: ❌ ERROR
See detailed report in MegaLinter reports |
ravindrapalaskar17
pushed a commit
that referenced
this pull request
May 3, 2024
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
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 is Internal PR for the base work of: -Extend the api guidelines with a concrete ruleset.
What type of PR is this?
enhancement/feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes camaraproject#15
Special notes for reviewers:
Decision outstanding whether spectral or Megalinter should be used.