Elad Chen

How about this:  An example: Let's say .github/workflows/pull-request.yml exists, and the suggested checkbox above is checked, and user John / DEV team is configured. Workflow ".github/workflows/pull-request.yml" will **not** be...

I am not a 100% sure but I have a feeling a dedicated github app can be written to accommodate my suggestion, while waiting for a response/solution from the github...

v2 docs: https://v2.dinerojs.com/docs/faq/how-can-i-create-dinero-objects-from-floats They are outdated though... currency.base might be a number or an array of numbers :|

Here's what I ended up writing: ```ts import * as Postgres from 'pg'; import { hrtime } from 'node:process'; const hrtimeToMs = (value: bigint) => Number(hrtime.bigint() - value) / 1000000;...

Wouldn't it be possible to patch the pg-pool still? You should be able to patch the exported `Pool` class. https://github.com/brianc/node-postgres/blob/6cd0aeb212d1672edd33499b2f4f858cf7ed9a79/packages/pg-pool/index.js#L66 You should be able to patch the above class prototype,...

This is driving my crazy ! I've been messing with it all day

I wouldn't address this issue using environment variables, Instead, I suggest the api should support receiving color mapping for the various outputs. @royriojas What do you think?

Just read that paragraph myself, and it was evident that pagination ought to be broken given that explanation. I guess I could try and help, how should we proceed?

I can do that. Any idea what the "next" header value is when the files exceed 300? On Sat, Sep 12, 2020, 21:52 Gregor Martynus wrote: > Hi Elad, >...

The workaround I'm using is to add the below entry to the tsconfig file ``` "paths": { "conventional-commits-parser": [ "node_modules/conventional-commits-parser/dist" ] }, ```