googleapis/pack-n-play

Issues

• pack-n-play: should run tests failed

  #182 opened 7 months ago by flaky-bot
  2

• Warning: a recent release failed

  #176 opened a year ago by failure-checker
  0

• Warning: a recent release failed

  #175 opened a year ago by failure-checker
  0

• Warning: a recent release failed

  #167 opened a year ago by failure-checker
  1

• Your .repo-metadata.json file has a problem 🤒

  #170 opened a year ago by repo-metadata-lint
  0

• Dependency Dashboard

  #104 opened a year ago by forking-renovate
  0

• Warning: a recent release failed

  #166 opened a year ago by failure-checker
  0

• Warning: a recent release failed

  #163 opened a year ago by failure-checker
  0

• Warning: a recent release failed

  #159 opened a year ago by failure-checker
  1

• Warning: a recent release failed

  #158 opened a year ago by failure-checker
  0

• Warning: a recent release failed

  #156 opened a year ago by failure-checker
  1

• Warning: a recent release failed

  #148 opened a year ago by failure-checker
  0

• [Policy Bot] found one or more issues with this repository.

  #126 opened a year ago by google-cloud-policy-bot
  0

• Let me use a fixtures directory

  #19 opened 6 years ago by JustinBeckwith
  1

• Let me run the code in my example

  #20 opened 6 years ago by JustinBeckwith
  3

• Action Required: Fix Renovate Configuration

  #106 opened 3 years ago by forking-renovate
  0

• output from commands not displayed when there is a failure

  #6 opened 5 years ago by soldair
  1

• use npm pack

  #56 opened 5 years ago by alexander-fenster
  1

• Publish a new version of the module

  #17 opened 5 years ago by JustinBeckwith
  4

• speed: remove redundant npm and gts commands

  #7 opened 6 years ago by soldair
  1

• Rename this project

  #22 opened 6 years ago by ofrobots
  4

• Add tests

  #21 opened 6 years ago by JustinBeckwith
  1

• Add build status, codecov, and synk badges to the README

  #18 opened 6 years ago by JustinBeckwith
  1

• An in-range update of @types/node is breaking the build 🚨

  #26 opened 6 years ago by greenkeeper
  3

• An in-range update of @types/node is breaking the build 🚨

  #16 opened 6 years ago by greenkeeper
  13

• Should we publish this under the `@google` npm scope?

  #3 opened 6 years ago by JustinBeckwith
  2

• Use a customized tsconfig.json

  #2 opened 6 years ago by JustinBeckwith
  0

• Configure renovate to keep deps up to date

  #9 opened 6 years ago by JustinBeckwith
  0

• Configure renovate to keep deps up to date

  #8 opened 6 years ago by JustinBeckwith
  1

• Set up CI

  #10 opened 6 years ago by JustinBeckwith
  1