# Repository checkout deployment

**URL:** <https://discuss.circleci.com/t/repository-checkout-deployment/6146>\
**Category:** Deployments\
**Tags:** git\
**Created:** [September 10, 2016, 8:51am UTC](https://discuss.circleci.com/t/repository-checkout-deployment/6146 "2016-09-10T08:51:44Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![tom](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/tom/32/27680_2.png) [@tom](https://discuss.circleci.com/u/tom)\
**Post date:** [September 12, 2016, 1:55pm UTC](https://discuss.circleci.com/t/repository-checkout-deployment/6146/2 "2016-09-12T13:55:49Z")

</div>

This should definitely be possible. This blog post, although it’s not exactly what you’re looking to do, should give you a good starting point:

> **[CircleCI Hacks - Automate the Decision to Skip Builds Using a Git Hook](https://circleci.com/blog/circleci-hacks-automate-the-decision-to-skip-builds-using-a-git-hook/)**
>
> How to use Git hooks and \[ci skip\] or \[skip ci\] to automate skipping trivial builds.

Instead of modifying the commit message with `[skip ci]` you could add variations appropriate to your needs.

Then on CircleCI via `circle.yml` you can inspect the git commit message (see here for how: [Git Commit Message in Environment Variable](https://discuss.circleci.com/t/git-commit-message-in-environment-variable/533)) and run deployment steps conditionally based on if the relevant string is found in the commit message.

If you get something like that working we’d be delighted if you wanted to share the steps you took / any gotchas.

---

_[View the full topic](https://discuss.circleci.com/t/repository-checkout-deployment/6146)._