In order to make editing the mapping seemlessly, there exists a special Keystone.guru instance which can be found at https://mapping.keystone.guru/. If you want to make adjustments to the mapping, do it there. You can also make adjustments to the mapping on your local machine, but only if you know what you're doing. If you adjust the mapping on the special mapping site, a merge request is eventually created which will ask to merge your mapping changes from the mapping branch into development. This is important to keep things going smoothly and to ensure a proper review is done before you actually merge mapping changes. I've also historically given out access to some people so they can create new mappings for usually old dungeons. With this extra review step, I can double check if they only changed what they were supposed to and didn't accidentally break something.

If you want to make a change to the mapping, be it to add a new mapping version, add a new dungeon, pretty much anything, you go to this environment. You make your changes, and wait for the pull request to show up. A cron job checks every 5 minutes of the latest change to any mapping was done at least 1 hour ago, and if it is, it will create a new merge request. The 1 hour wait is there to prevent the mapping from being saved/updated every 5 minutes while you're actively editing the mapping, potentially causing issues along the way.

If your time is valuable to you you may want to force this process, though. Log into the server, navigate to /var/www/html/mapping.keystone.guru and run the following command:

php artisan mapping:sync --force=true

This will always create a backup of the current mapping, add any added files to Git push the commit and create a pull request (if one didn't already exist). This is exactly what the cron job does as well, just without having to wait.