Lambda for (reverse) proxying GitHub API requests from the frontend for getting live repositories and issues data.
Changes submitted to src/*.js are uploaded manually to the AWS Lambda function console. Currently there are two Lambdas used
- issues - Fetches issues from the GitHub API for a given project name and repository name
- repositories - Fetches repositories from the GitHub API for a given project name and repository type (org or user)
For contributing to this project and testing the output locally, you will need
- NodeJS 8.x
- Yarn 1.x
- Create tmp/ directory in the root of the project
- Set envrionment variable for devleopment:
export NODE_ENV=development
- Export a GitHub personal access token:
export ACCESS_TOKEN=XXX
yarn lint
- Validatse all JS and JSON passes lintingyarn function:issues
- Run src/issues.js and by default output the file in tmp/yarn function:repositories
- Run src/repositories.js and by default output the file in tmp/
- Merge all changes into master
- Bump package.json,
git tag
and push everything to master - Upload the contents of src/index.js to Lambda
- Create Release Notes in GitHub