# Pushing changes with git to Heroku without triggering a buildpack.

**URL:** <https://forum.djangoproject.com/t/pushing-changes-with-git-to-heroku-without-triggering-a-buildpack/6806>\
**Category:** Using Django\
**Created:** [February 27, 2021, 12:02pm UTC](https://forum.djangoproject.com/t/pushing-changes-with-git-to-heroku-without-triggering-a-buildpack/6806 "2021-02-27T12:02:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Drone4four](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/drone4four/32/3072_2.png) [@Drone4four](https://forum.djangoproject.com/u/Drone4four)\
**Post date:** [February 27, 2021, 12:02pm UTC](https://forum.djangoproject.com/t/pushing-changes-with-git-to-heroku-without-triggering-a-buildpack/6806/1 "2021-02-27T12:02:54Z")

</div>

Heroku offers [a buildpack service](https://devcenter.heroku.com/articles/buildpacks) which enables admins to deploy the Python environment, install packages with pip, and assemble the slug. A buildpack is triggered whenever a commit from master is pushed to Heroku. For those who might be familiar with Django but not with Heroku, here on pastebin is [the full output](https://pastebin.com/hEA8pF59) showing the buildpack in action.

The problem is, even if I make a trivial change, pushing master to Heroku builds from source which I feel is usually completely unnecessary. Perhaps after making many major commits, deploying using a build pack is a good idea. But most of the time, I just want to push small source code changes.

For anyone who is familiar with deploying Django with Heroku, how do I push my changes without triggering the buildpack every time?

I’ve tried variations of git push parameters such as:

- `(local venv) $ git push heroku`
- `(local venv) $ git push heroku master`
- `(local venv) $ git push heroku origin/master`

The first two build. When I run the last one there in the shell for my development environment, git returns this output, verbatim:

```auto
(local venv) $ git push heroku origin/master
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 16 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (6/6), 649 bytes | 649.00 KiB/s, done.
Total 6 (delta 4), reused 0 (delta 0), pack-reused 0
remote: Pushed to branch other than [main, master], skipping build.
To ssh://heroku.com/<project-name>.git
 * [new reference] origin/master -> origin/master
(local venv) $

```

So that looks like the buildpack is not running, right? However, when I peak at the Heroku dashboard, in the logs, I can see the buildpack running in the background. So `$ git push heroku origin/master` runs the buildpack silently locally.

I really just want to be able to push a change and test it instantly without having to wait 2 minutes for the slug to assemble. Is my only option to disable the buildpack altogether?

I’ve used Google search terms such as:

- ‘push changes to heroku without buildpack’
- ‘push heroku no buildpack’
- ‘heroku buildpack silent’ **#** which turns up only 93 search results
- ‘heroku buildpack “silent”’ **#** which turns up 497,000 search results

All those search results are not relevant to my question. I am getting nowhere with Google.

---

<div class="post-metadata">

**Author:** ![marcorichetta](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.djangoproject.com/marcorichetta/32/26473_2.png) [@marcorichetta](https://forum.djangoproject.com/u/marcorichetta)\
**Post date:** [February 28, 2021, 1:19am UTC](https://forum.djangoproject.com/t/pushing-changes-with-git-to-heroku-without-triggering-a-buildpack/6806/2 "2021-02-28T01:19:33Z")

</div>

AFAIK you can’t skip buildpacks. Buildpacks transform your project source code into something runnable by Heroku called _slug_.

From Heroku docs:

> Slugs are compressed and pre-packaged copies of your application optimized for distribution to the [dyno manager](https://devcenter.heroku.com/articles/dynos#the-dyno-manager). When you `git push` to Heroku, your code is received by the slug compiler which transforms your repository into a slug. Scaling an application then downloads and expands the slug to a dyno for execution.

That said, you can [create your own slugs](https://devcenter.heroku.com/articles/platform-api-deploying-slugs).
