# Unable to push changes to Staging

**URL:** <https://community.forestadmin.com/t/unable-to-push-changes-to-staging/5540>\
**Category:** Help me!\
**Created:** [November 17, 2022, 3:41pm UTC](https://community.forestadmin.com/t/unable-to-push-changes-to-staging/5540 "2022-11-17T15:41:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Adil\_Niaz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/adil_niaz/32/466_2.png) [@Adil\_Niaz](https://community.forestadmin.com/u/Adil_Niaz)\
**Post date:** [November 17, 2022, 3:41pm UTC](https://community.forestadmin.com/t/unable-to-push-changes-to-staging/5540/1 "2022-11-17T15:41:35Z")

</div>

## Feature(s) impacted

Forest CLI

## Observed behavior

Unable to push from Development to Staging.

Attempts to push results into the following behaviour:

```javascript
forest push
? Push branch branch-name onto Production (Y/n)

```

and

```javascript
forest push --force
× Failed to push branch: cannot "push" to reference environment, please use "deploy"

```

Meanwhile _deploy_ works as expected.

## Context

- Project name: Kokoon.1
- Environment name: Staging
- Agent type & version: forest-express-sequelize : 8.5.9

Development’s origin is Production.  
Staging’s origin is Production.

---

<div class="post-metadata">

**Author:** ![Florian\_Gonzales](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/florian_gonzales/32/5541_2.png) [@Florian\_Gonzales](https://community.forestadmin.com/u/Florian_Gonzales)\
**Post date:** [November 17, 2022, 4:56pm UTC](https://community.forestadmin.com/t/unable-to-push-changes-to-staging/5540/2 "2022-11-17T16:56:55Z")

</div>

Hello @Adil_Niaz ,

Thanks for sending us a message! It seems that your Development environment has for origin your production, if it is supposed to be based on your Staging environment could you use the forest set-origin command ( [set-origin - Developer guide](https://docs.forestadmin.com/developer-guide-agents-nodejs/deploying-to-production/forest-cli-commands/set-origin) ). Once you run this command you should be able to run your push command 🙂

Please let me know if this solves your problem 🙏

Kind regards,

Florian Gonzales

---

<div class="post-metadata">

**Author:** ![Adil\_Niaz](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/adil_niaz/32/466_2.png) [@Adil\_Niaz](https://community.forestadmin.com/u/Adil_Niaz)\
**Post date:** [November 18, 2022, 8:55am UTC](https://community.forestadmin.com/t/unable-to-push-changes-to-staging/5540/4 "2022-11-18T08:55:29Z")

</div>

Hi,

It used to work with Production as origin for Development before. But I will change the origin to Staging for the next feature.

Thanks.

---

<div class="post-metadata">

**Author:** ![Florian\_Gonzales](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/florian_gonzales/32/5541_2.png) [@Florian\_Gonzales](https://community.forestadmin.com/u/Florian_Gonzales)\
**Post date:** [November 18, 2022, 1:04pm UTC](https://community.forestadmin.com/t/unable-to-push-changes-to-staging/5540/5 "2022-11-18T13:04:17Z")

</div>

Hello @Adil_Niaz ,

Great! Don’t hesitate to come back to us if you encounter any problem when you make this change.

Kind regards,

Florian