Revert "Update the link from blockchain.info to blockchain.com"

This commit is contained in:
Pawel Borkar
2021-03-31 14:15:04 +05:30
committed by GitHub
parent 53b482c1b8
commit d715512429
19 changed files with 3732 additions and 1175 deletions
+6 -16
View File
@@ -4,43 +4,35 @@
opened to market company APIs that offer paid solutions. This API list is not a marketing tool, but a tool to help the
community build applications and use free, public APIs quickly and easily. Pull requests that are identified as marketing attempts will not be accepted.
>
> Please make sure the API you want to add has a full free access or at least a free tier before submitting.
>
> Thanks for understanding! :)
## Formatting
Current API entry format:
| API | Description | Auth | HTTPS | CORS |
| API | Description | Auth | HTTPS | Link |
| --- | --- | --- | --- | --- |
| API Title(Link to API documentation) | Description of API | Does this API require authentication? * | Does the API support HTTPS? | Does the API support [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS)? * |
| API Title | Description of API | Does this API require authentication? * | Does the API support HTTPS? | Link to API webpage |
Example entry:
```
| [NASA](https://api.nasa.gov) | NASA data, including imagery | No | Yes | Yes |
| NASA | NASA data, including imagery | No | Yes | [Go!](https://api.nasa.gov) |
```
\* Currently, the only accepted inputs for the `Auth` field are as follows:
Currently, the only accepted inputs for this field are as follows:
* `OAuth` - _the API supports OAuth_
* `apiKey` - _the API uses a private key string/token for authentication - try and use the correct parameter_
* `X-Mashape-Key` - _the name of the header which may need to be sent_
* `No` - _the API requires no authentication to run_
\* Currently, the only accepted inputs for the `CORS` field are as follows:
* `Yes` - _the API supports CORS_
* `No` - _the API does not support CORS_
* `Unknown` - _it is unknown if the API supports CORS_
_Without proper [CORS configuration](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) an API will only be usable server side._
Please continue to follow the alphabetical ordering that is in place per section. Each table column should be padded with one space on either side.
If an API seems to fall into multiple categories, please place the listing within the section most in line with the services offered through the API. For example, the Instagram API is listed under `Social` since it is mainly a social network, even though it could also apply to `Photography`.
This project now offers a [JSON version](json/) of the list of services. These files are automatically updated as part of the Continuous Integration process, so there is no need to update them as part of the contribution.
## Pull Request
After you've created a branch on your fork with your changes, it's time to [make a pull request][pr-link]!
@@ -56,7 +48,6 @@ merge conflicts will be less likely. See more detailed instructions [here][synci
* Create a [branch][branch-link] for your edits.
* Contribute in the style of the project as outlined above. This makes it easier for the collaborators to merge
and for others to understand and maintain in the future.
* Please make sure you squash all commits together before opening a pull request. If your pull request requires changes upon review, please be sure to squash all additional commits as well. [This wiki page][squash-link] outlines the squash process.
### Open Pull Requests
@@ -79,5 +70,4 @@ Thanks for being a part of this project, and we look forward to hearing from you
[pr-link]: <https://help.github.com/articles/creating-a-pull-request/>
[remote-link]: <https://help.github.com/articles/configuring-a-remote-for-a-fork/>
[syncing-link]: <https://help.github.com/articles/syncing-a-fork>
[squash-link]: <https://github.com/todotxt/todo.txt-android/wiki/Squash-All-Commits-Related-to-a-Single-Issue-into-a-Single-Commit>
+10 -11
View File
@@ -1,12 +1,11 @@
<!-- Thank you for taking the time to work on a Pull Request for this project! -->
<!-- To ensure your PR is dealt with swiftly please check the following: -->
- [ ] My submission is formatted according to the guidelines in the [contributing guide](CONTRIBUTING.md)
- [ ] My addition is ordered alphabetically
- [ ] My submission has a useful description
- [ ] The description does not end with punctuation
- [ ] Each table column is padded with one space on either side
- [ ] I have searched the repository for any relevant issues or pull requests
- [ ] Any category I am creating has the minimum requirement of 3 items
- [ ] All changes have been [squashed][squash-link] into a single commit
Thank you for taking the time to work on a Pull Request for this project!
[squash-link]: <https://github.com/todotxt/todo.txt-android/wiki/Squash-All-Commits-Related-to-a-Single-Issue-into-a-Single-Commit>
To ensure your PR is dealt with swiftly please check the following:
- [ ] Your submissions are formatted according to the guidelines in the [contributing guide](CONTRIBUTING.md).
- [ ] Your changes are made in the [README](../README.md) file, not the auto-generated JSON.
- [ ] Your additions are ordered alphabetically.
- [ ] Your submission has a useful description.
- [ ] Each table column should be padded with one space on either side.
- [ ] You have searched the repository for any relevant issues or PRs.
- [ ] Any category you are creating has the minimum requirement of 3 items.
-29
View File
@@ -1,29 +0,0 @@
name: "Run tests"
on:
schedule:
- cron: '0 0 * * *'
push:
branches:
- master
pull_request:
branches:
- master
env:
FORMAT_FILE: README.md
jobs:
test:
name: 'Validate README.md'
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v2
- name: Validate Markdown format
run: build/validate_format.py ${FORMAT_FILE}
- name: Validate pull request changes
run: build/github-pull.sh ${{ github.repository }} ${{ github.event.pull_request.number }} ${FORMAT_FILE}
if: github.event_name == 'pull_request'
-22
View File
@@ -1,22 +0,0 @@
name: "Validate links"
on:
schedule:
- cron: '0 0 * * *'
push:
branches:
- master
env:
FORMAT_FILE: README.md
jobs:
test:
name: 'Validate links'
runs-on: ubuntu-latest
steps:
- name: Checkout repository
uses: actions/checkout@v2
- name: Validate all links from README.md
run: build/validate_links.py ${FORMAT_FILE}