Clients: should pass eslint for a given client failed

Open
  • Is something wrong?
#3,662 22 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
nodejs, typescript
Domain
ci-cd, tooling

Research direction

Start with the failed build linked in the issue and inspect commit 682fbb869189ae92b3e9a194d37d0548af0c1f92 to identify which client fails eslint. Reproduce the check for that client and confirm that the client passes eslint when the work is complete.

Written by the indexing model from the issue text.

Description

flakybot: flaky flakybot: issue priority: p2 type: bug

Note: #3359 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.

commit: 682fbb869189ae92b3e9a194d37d0548af0c1f92
buildURL: Build Status, Sponge
status: failed

Dominant language
TypeScript
Stars
12.3k
Forks
2k
Avg merge
3d 10h
Merged PRs (30d)
9

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-api-nodejs-client

All issues in googleapis/google-api-nodejs-client

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.