---
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


---

# Work with changes in Git

# Work with changes in Git {#ariaid-title1}

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

Developers using App Engine Studio (AES) can pull and commit changes in their Git repository.  
Note:  
If you're using source control to collaborate with other developers, only changes that have been checked in are available to other developers. For example, if an admin creates a new flow for an app that's linked to Git, the new flow won't be available in the app for other AES users until the admin checks the flow into Git.
* **[Pull changes from a repository](https://servicenow-prod.fluidtopics.net/r_1JUTDkDjMYIfQZQlleew)**   
  App developers using App Engine Studio (AES) can pull changes from a linked Git repository to apply remote changes to the local instance.
* **[Commit changes to a repository](https://servicenow-prod.fluidtopics.net/4j2iTZOoDfvXE~12629UPQ)**   
  Commit changes made in your application in App Engine Studio (AES) to a linked Git repository. You can either select a few changes to commit, or commit all changes on the instance at once.