# Deploying a specific commit instead of a branch/tag

**URL:** <https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442>\
**Category:** How Do I?\
**Created:** [November 18, 2025, 9:55am UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442 "2025-11-18T09:55:06Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mark90](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/mark90/32/406_2.png) [@Mark90](https://community.okteto.com/u/Mark90)\
**Post date:** [November 18, 2025, 9:55am UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442/1 "2025-11-18T09:55:06Z")

</div>

Hi, I am curious if it is possible to deploy a dev environment based on a commit SHA, without having to create a branch/tag for it?

---

<div class="post-metadata">

**Author:** ![jona](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/jona/32/353_2.png) [@jona](https://community.okteto.com/u/jona)\
**Post date:** [November 18, 2025, 4:59pm UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442/2 "2025-11-18T16:59:13Z")

</div>

Hi @Mark90 !

You should be able to set the commit SHA as your current working tree in your local filesystem, and then run the `okteto deploy` command, as follows:

```auto
git checkout <Commit SHA>
okteto deploy

```

Would that accomplish your use-case objective?

Thanks!

---

<div class="post-metadata">

**Author:** ![Mark90](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/mark90/32/406_2.png) [@Mark90](https://community.okteto.com/u/Mark90)\
**Post date:** [November 20, 2025, 9:39am UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442/3 "2025-11-20T09:39:43Z")

</div>

Hi Jona,

Locally that would work, but we’re using `okteto pipeline deploy` to deploy several (27) different repositories. It has the `--branch` option but it doesn’t seem to accept commit SHA. If this option doesn’t exist, perhaps I should create a feature request?

Thanks, Mark

---

<div class="post-metadata">

**Author:** ![Mark90](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/mark90/32/406_2.png) [@Mark90](https://community.okteto.com/u/Mark90)\
**Post date:** [January 5, 2026, 7:45am UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442/4 "2026-01-05T07:45:56Z")

</div>

Hi @jona, not sure if you got my last reply. Should I create a feature request?

---

<div class="post-metadata">

**Author:** ![jona](https://sea1.discourse-cdn.com/flex019/user_avatar/community.okteto.com/jona/32/353_2.png) [@jona](https://community.okteto.com/u/jona)\
**Post date:** [January 5, 2026, 2:44pm UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442/5 "2026-01-05T14:44:45Z")

</div>

> [@Mark90](#):
>
> different repositories. It has the `--branch` option but it doesn’t seem to accept commit SHA. If this option doesn’t exist, perhaps I should create a feature request?

Hi @Mark90 , I will go ahead and create a feature request on your behalf for this. I can update on this thread as I receive updates on the feature request. Thanks for the heads up and the additional information.

Thank you!

---

<div class="post-metadata">

**Author:** ![rodrigue](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@rodrigue](https://community.okteto.com/u/rodrigue)\
**Post date:** [February 5, 2026, 6:32pm UTC](https://community.okteto.com/t/deploying-a-specific-commit-instead-of-a-branch-tag/1442/6 "2026-02-05T18:32:47Z")

</div>

Okteto pipeline deploy does not support commit SHA. --branch only works with branches and tags because the pipeline needs a ref that it can resolve, not a detached commit. Local checkout works, but pipelines don’t.

A workaround is to add a temporary tag to each commit, or you could file a feature request. This is a good use case for multi-repo pipelines.