Push to your Repository

Pushing your Component or whole App to GitHub

To sync your Component or App code to your GitHub repository, you'll need to first get your GitHub API Key. Once you have the API Key, you can start choose your Repo, Branch and Path to push to.

Getting the API Key

  1. Go to settings on GitHub

2. Scroll down to the Developer Settings in the left panel

3. Click Personal access tokens in the left side

4. Click on Generate new token button

5. Give a name to the key

Preferably, you should name it something so you remember that it is the key for Quest. You should not use this key for anything else other than the GitHub Quest integration. Set the "Expiration" to "No expiration" to avoid problems with it later.

6. Check the repo checkbox, to give all the permissions inside the repos

7. Scroll down and click Generate token

Copy the generated token for use in the next step. Please note that you can copy it only one time. If you need to do this again for some reason, you will need to regenerate the token.

Adding your API Key in Quest

Your API Keys are added at the Workspace level and can be shared across all Apps within the workspace. You cannot share the keys across Workspaces in Quest. You need to generate a new token per Workspace. Any team members in that Workspace can add and manage API Keys.

Pushing your App to the repo

In the Export tab for the App that you're working on, in the top of the page, toggle to "Push to Repository" and you will find the Repository Settings.

From here you can select the API Key that you added or other team members have added. After that, you can choose your Repo, Branch and Path. Once you choose your Path, Quest will auto-save your choices. The "Push App" button will become enabled and you will then be able to push your entire app to your repository.

For both Image and Fonts Paths, the paths you specify will be relevant to the Path in your Branch that you choose. This is different for how it works with Downloading the App as in that case it will only be a reference to those locations in the file and you will need to manually move any asset folders that are downloaded.

Note: You will need to have these Repository Settings all filled out in order to be able to export individual components from the Quest Editor.

Pushing individual Components

In the Quest Editor, if you have all your settings previously set up in the steps above, you will be able to push individual components to your Repository. If you don't have this set up on the App level, the Push button will be disabled. This is a quicker way to push things as it will only collect the relevant files to push and not everything in your App.

Last updated