---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Queue a local change for a push

# Queue a local change for a push {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Application developers can queue a local change for a push to ensure the changes are
available to other developers.

## Procedure

1. Navigate to AllTeam DevelopmentTeam Dashboard.
2. Filter the Local Changes list to show only the changes that are ready to push.  
   For example, filter the list to show only the changes associated with a
   particular application.  
3. Click Queue All For Push.
4. Review the Ready to Push list to ensure that the correct changes are in the queue.  
   This step is a recommended best practice.

   | Option | Description |
   | To remove changes from the queue | Select the check boxes beside the rows and select Do Not Push from the Actions choice list. |
   | To remove changes from the queue and choose to ignore them instead | Select the check boxes beside the rows and select Ignore This Change from the Actions choice list. |
   |-|-|

   {#t_QueueALocalChangeForAPush__choicetable_c1h_cgc_bq}  
   Note:  
   For the Local Changes list, click Reset Filter to remove any filter conditions you added and see all the local changes that have not been queued or ignored.

*[\>]: and then