GitHub Desktop is one of many third party tools that can be used for accessing web pages hosted on the Artsman Cloud in a git repository. Git is a distributed version-control system. It's great at tracking who made changes to what and when.
To setup access to your specific company web pages via Git, email support@artsman.com with the full name of the employee who will be allowed to make changes to your pages, and their company email address. For security and tracking purposes, only employee specific email addresses are accepted, like "johnsmith@example.com".
To use GitHub Desktop simply download and install the program. Clone the git repository pages to your computer for editing locally. After edits are made Commit and Push to the master branch of the repository directly through GitHub Desktop.
Only previously customized web pages will appear in the Artsman Cloud git repository for your organization. If the page you wish to edit does not appear on your local machine it may not have previously been edited. You'll need to download the default responsive pages and move that desired page to the corresponding folder on your local machine before making edits. Your repository should only contain customized web pages.
Remember to download the latest responsive pages each time before you begin making edits. |
The GitLab Repository URL is needed when cloning the repository locally. The steps below should only need to be done once per repository during the initial setup.
Login information is requested through the Artsman Support team. If you have not previously been provided access please email the support team. When access is granted an email will be sent directly from GitLab to your email with steps for setting a password and logging in.
This will copy the URL for the repository to your computers clipboard making it ready to paste into GitHub Desktop for cloning.
You may be prompted to enter the your login credentials for the GitLab repository.
The web pages are now copied to your local computer for editing. When editing new pages always make sure to use the latest version of the responsive pages to ensure the page you are working on contains all the latest features.
It's important to always start any web page editing by Pulling changes from the existing repository. This ensures any changes made that are not currently in your local repository are pulled to your machine before you begin making edits.
Missing the step of Pulling means you may need to Rebase before completing the process of adding your changes to the repository. Rebasing a repository with conflicting changes requires a deeper understanding of git. For further information please see GitHub online documentation for assistance.
GitHub Desktop is great at picking up when new pages are available in a repository. Changes are often detected within moments of opening the program and notifications can be seen in the main display.
Any changes previously waiting to be pulled will now be in the folder on your local machine. The web pages are ready to be edited.
Once web pages have been editing locally they need to be Committed before they are Pushed to the Artsman cloud repository. This allows you to add select changes while continuing to make edits.
These changes are now ready to be pushed to the repository.
Pushing changes moves the pages up to the Artsman git repository. Only pages that have been Committed can be Pushed. Once the pages have been pushed they run through a series of tests before they are available to be accessed by the web listener. To see edits following the test process you many need to clear the cache on the web listener.
Changes have now been added to the online repository. Most changes will appear online within moments of editing. Items that are more deeply cached may require a clear cache and occasionally a restart of the Theatre Manager server. If you do not see your changes after clear the cache in Theatre Manager please contact the support team assistance.