> For the complete documentation index, see [llms.txt](https://docs.datajet-app.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datajet-app.com/integrations/github/use-one-codebase-across-multiple-shopify-stores.md).

# Use one codebase across multiple Shopify stores

The GitHub repository might be connected to multiple DataJet apps installed on multiple Shopify stores.

Let's assume you have a repository with a file named *webhook/order-created.dj* and two Shopify stores:

* Store AU
* Store NZ

You can connect DataJet on both stores to a single GitHub repository. For each store, create a webhook script: *order-created.dj* and connect it to the same *webhook/order-created.dj* file*.* Now, anytime you push changes to your *webhook/order-created.dj* file, both stores will be updated automatically. Similarly, if you update your script through the DataJet Developer Console on Store AU, Store NZ will be updated as well.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datajet-app.com/integrations/github/use-one-codebase-across-multiple-shopify-stores.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.