Update v3.0.json #2722
Open
Update v3.0.json #2722
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
there is a duplicate apikey, it should be http and not apikey
Contributor
|
@Learnfr Can we please change the commit message to follow semantic commits |
Author
|
@mnaumanali94 yes you could change the commit message |
Contributor
|
@Learnfr Considering its your PR it would be the easiest for you to amend the commit or close this PR and create a new one. We would really appreciate that. Once these tests/linting passes we can review it. |
Contributor
|
@Learnfr Gentle reminder to take a look at this if you can 🙏🏼 |
Contributor
|
You should be able to update it on your fork doing something like: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
there is a duplicate apikey, it should be http and not apikey
Fixes #[ISSUE_NUMBER].
Checklist
Does this PR introduce a breaking change?
Screenshots
If applicable, add screenshots or gifs to help demonstrate the changes. If not applicable, remove this screenshots section before creating the PR.
Additional context
Add any other context about the pull request here. Remove this section if there is no additional context.