danger / danger/danger-js

Use danger standalone? (danger triggers github rate limit exceeding)

Open
#989 3 comments 3 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
5.5k
Forks
381
Avg merge
2h 8m
Merged PRs (30d)
6

Description

Hey,

i am running danger standalone in a kubernets pod-container.
The command i use to run danger looks like that:

```sh
export DANGER_GITHUB_API_TOKEN=${GIT_TOKEN}
danger pr https://github.com/${GIT_OWNER}/${GIT_REPO}/pull/${GIT_PULL_REQUEST}
```

This is running fine and gives the expected results.
My problem is, that our repo seems to be really large and while running that process danger makes about 1900 calls to the github api, which lets us run into the rate limit really fast.

Now i wanted to ask, if i can somehow avoid that?
I am not really sure where to start here to avoid the github api calls.

thx in advance!

Contributor guide

Open the contributing guide

Research direction

The issue names only the standalone `danger pr` command and its GitHub API token environment variable; no source files, tests, or entry points are provided. Start by reproducing that command in the Kubernetes pod and measuring which GitHub API requests occur. Done would mean defining and validating a way to avoid the excessive requests or documenting that it is not possible.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, kubernetes, typescript
Domain
api, devtools, infrastructure
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.