JS library to interact with Forgejo API to work with notifications https://forgejo-notifications-core.docs.forgeflux.org/
Go to file
Aravinth Manivannan d2083b26ca
fix: enable fetch api in jest
2023-09-18 19:05:53 +05:30
.reuse feat: init 2023-09-16 15:12:35 +05:30
LICENSES feat: init 2023-09-16 15:12:35 +05:30
integration feat: write account details to json file as part of create_access_token 2023-09-18 19:05:13 +05:30
src feat: migrate to typescript 2023-09-18 17:56:40 +05:30
.gitignore feat: setup jest and typescript 2023-09-18 17:56:31 +05:30
.nvmrc feat: setup jest and typescript 2023-09-18 17:56:31 +05:30
Makefile feat: deploy and configure forgejo instance for testing 2023-09-17 01:59:08 +05:30
README.md feat: document CORS headache 2023-09-18 19:04:30 +05:30
docker-compose-dev-deps.yml chore & fix: enable CORS to work with Forgejo API 2023-09-18 19:02:09 +05:30
jest.config.ts fix: enable fetch api in jest 2023-09-18 19:05:53 +05:30
package.json fix: enable fetch api in jest 2023-09-18 19:05:53 +05:30
pnpm-lock.yaml fix: enable fetch api in jest 2023-09-18 19:05:53 +05:30
setupJest.js fix: enable fetch api in jest 2023-09-18 19:05:53 +05:30

README.md

Requires your Forgejo instance admin to enable CORS for at least the origin which serves the notification panel. Please see here for more information.

NOTE: The test forgejo configuration may be insecure for your usecase since it allows CORS for all origins with the widest possible surface.