@EIJason
So I made a fork of your osticket intallation and I made those certain changes.
Which repo did you fork? My repo at JediKev/osTicket
or the main repo at osTicket/osTicket
? If I were you I would fork the main repo at osTicket/osTicket
as this is always the most up-to-date. I very rarely keep my base branches up-to-date in my public fork, only on my local clones. The 1.14.x
series used to be on develop-next
but now it is on develop
, so I would use this branch to stay up-to-date with the latest changes.
Now I was under the impression that when you make changes to the your osticket my fork is automatically updated.
Now this is not entirely true. Most of the time you will need to clone your fork somewhere locally $ git clone <clone-url>
, add osTicket as a remote via $ git add remote <remote-name> <main-repo-url>
, fetch the latest changes via $ git fetch <remote-name>
, and then merge the fetched branch to your local clone via $ git merge <remote-name>/<branch>
. Here is an example:
$ git clone https://github.com/your/fork.git
$ cd <cloned-project-folder>
$ git checkout develop
$ git add upstream https://github.com/osTicket/osTicket.git
$ git remote -v (to see a list of remotes)
$ git fetch upstream
$ git merge upstream/develop (make sure you are on the develop branch first with `$ git checkout develop`)
So I copied the whole of my OSTicket fork back over my live files but the version didnt update?
If you are going to use a Git clone then it will always show the version like that. The only time it will show the actual version number is if you either package osTicket or use the downloads from our site or the Github Releases page.
Cheers.