Feature Requests

You can use Render Deploy Hooks to trigger a build from an external CI service like GitHub Actions or CircleCI. https://render.com/docs/deploy-hooks It would be nice to automate this process based on CI status check events that GitHub already emits on the repo.

Call GitHub Deployments API automatically after a Render deployment is started, canceled, successful, etc. It would be really useful to see all the currently running environments on GitHub with all the details: environment url log url deployment details date & time of deployment commit deployed etc.

Sometimes, a service is dependent on another service, like when a background worker is dependent on the main service getting updated and running migrations. It would be nice to be able to define this relationship in Render, so things like deploys can run sequentially.

Ability to view the time it takes to build.

Useful for seeing at a glance how build/deploy times are changing over time.

Solutions like yarn workspaces, turborepo, lerna, nx, etc... usually hoist dependencies at the root level of the monorepo. This means that when installing a single app, e.g. the API, even if you're using the suggested Render's monorepo rootFolder and/or buildFilters , you will still install all of the dependencies across all of your apps and packages. This will result in increased build time and in a non-scalable infrastructure. Netlify described how they solved their caching strategy to address yarn workspaces. I provide additional context here .

I use dependabot on github to automatically raise PRs when there are new versions of dependencies. I also have several services for my app, so what happens is that each of these PRs will spin up several dependencies and this is becoming quite expensive. What would be really useful is to be able to specify build filters for each service that prevent it being built depending on what has changed. This might also be a solution to https://feedback.render.com/features/p/turn-off-previews-for-specific-prs

in addition to previewsExpireAfterDays to not count weekends

Let us chose which version of pnpm we would like to use by specifying it in package.json like for node.

Our builds seem to run on a shallow git clone i.e. git fetch --depth=1 . I verified this by running the following build command Oct. 31 05:25:25 PM ==> Running build command 'git --version && git rev-parse --is-shallow-repository && yarn docs:build'... Oct. 31 05:25:25 PM git version 2.20.1 Oct. 31 05:25:25 PM true This is a problem for our static site build using vuepress (or docusaurus) because they both use git history information to autogenerate last edit information for pages by querying the git repo's history for the file. This history is not available in shallow clones. Now, I tried unshallowing in the build command but somehow it seems that's blocked (silently fails to do its job) in the CI environment Oct. 31 05:39:23 PM ==> Running build command 'git --version && git rev-parse --is-shallow-repository && git fetch --unshallow && git rev-parse --is-shallow-repository && yarn docs:build'... Oct. 31 05:39:23 PM git version 2.20.1 Oct. 31 05:39:23 PM true Oct. 31 05:39:23 PM true Is there any way I can get the render build runners to run a CI build with a full clone of the git repo?