Richard Schneeman

That didn't work https://github.com/zombocom/dead_end/tree/schneems/block-node-attempt-2 does seem to hold though. It doesn't use any of the weird-ish new ideas here. Instead, it doubles down on existing basics by re-writing the whole...

@marcospb19 I like the idea. I'm trying to use this library to map desired operations to human readable reasons why they are or aren't possible. For example, instead of simply...

I'm not sure, do we know how many people are using `ci:debug` ? It's so new, it's probably okay to default to this behavior. Do all the processes of the...

I guess i'm talking about the case where the build fails before the buildpack has the opportunity to even write the `ruby.sh` file. We could re-write the ruby buildpack to...

Instead of doing this on a customer's app we can copy their config to another app and run ci: ``` heroku sudo api get /pipelines//stage/test/config-vars -v 3.pipeline | heroku api...

This didn't work because it copied over database url values which rails (thank goodness) won't let you blow away the entire contents of a database with a thing like `rake...

I got a bit distracted in my quest for louder jams. I found https://github.com/cab404/ploopy-mods/tree/736a983d29a48fdbb119229f41d20266aa45e459/newcap from the Subreddit some time ago but haven't gotten around to trying any of them. Seems...

Thanks again for the docs, and validating my feedback. You're welcome to close the issue and reference it (or keep it open if you want until the re-write is done).

Either confirm they exist or add them

We are still missing some of the metadata structs ```rust #[derive(Deserialize, Serialize, Debug, Clone)] pub(crate) struct MetadataV1 { pub(crate) version: ResolvedBundlerVersion, } ```