feat(docs): Add badges for version, dependencies, and license to README.md
- Added a version badge to indicate the current version of the project. - Included a dependencies badge to show the status of project dependencies. - Added a license badge to clarify the licensing of the project. chore(ci): Update test workflow to improve coverage reporting - Updated the test.yml workflow to include coverage reporting using Codecov. - Ensured that the workflow runs on pushes and pull requests to main and develop branches.
This commit is contained in:
parent
319f1071bf
commit
24d0601168
2 changed files with 5 additions and 13 deletions
13
.github/workflows/test.yml
vendored
13
.github/workflows/test.yml
vendored
|
|
@ -32,15 +32,4 @@ jobs:
|
|||
uses: codecov/codecov-action@v3
|
||||
with:
|
||||
file: ./lcov.info
|
||||
fail_ci_if_error: false
|
||||
|
||||
- name: Create status badge
|
||||
if: github.ref == 'refs/heads/main' && github.event_name == 'push'
|
||||
uses: schneegans/dynamic-badges-action@v1.6.0
|
||||
with:
|
||||
auth: ${{ secrets.GIST_SECRET }}
|
||||
gistID: ${{ secrets.GIST_ID }}
|
||||
filename: vrcauthproxy-tests.json
|
||||
label: tests
|
||||
message: passing
|
||||
color: success
|
||||
fail_ci_if_error: false
|
||||
|
|
@ -2,7 +2,10 @@
|
|||
#### A VRChat API Authorization Proxy Service
|
||||
|
||||
[](https://github.com/PrideVRInc/VRCAuthProxy/actions/workflows/build.yml)
|
||||
[](https://github.com/PrideVRInc/VRCAuthProxy/actions/workflows/test.yml)
|
||||
[](https://github.com/PrideVRInc/VRCAuthProxy/actions/workflows/test.yml)
|
||||
[](https://github.com/PrideVRInc/VRCAuthProxy/releases)
|
||||
[](https://david-dm.org/PrideVRInc/VRCAuthProxy)
|
||||
[](https://opensource.org/licenses/MPL-2.0)
|
||||
|
||||
This authorization proxy service is for consuming the VRChat API in a multi-application / microservice architecture. Configure the proxy with the credentials for accounts you use to make API calls and direct your API clients to the proxy service instead of the VRChat API. The proxy server will handle the authorization call flow and caching of the authorization tokens for subsequent authorized calls.
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue