Source code storage service

-Every source code file is indexed on the server. Can be like a gist, for any file to be uploaded to the cloud.<br>-Viewing is based on searching the code for patterns. You go to create a new issue,<br>-Type in the issue description, and the service outputs a block of code where the issue should be located. By location, I mean the two lines of code that the issue is likely between. You can just right click the block of code in the issue description and click "apply fix". There will be a set of likely fixes generated with the first most likely option to resolve the issue selected. You can click apply fix, resolve the issue, and then just right click the block of code in the commit message and click copy to clipboard. Then, you just apply the commit, resolve the issue, then click commit and push. And the server will automatically auto resolve the issue with a url to the commit. <br>-The server also can create the issue automatically, for example if you make a pull request but never merge it, it will automatically add a ```WontFix``` tag and ```Close``` the issue with a canned response.<br>-There is a feature called "codex" where you can summarize the code based on the tags on the commit. For example if you commit something like this: ```[hardcore mode][rare items][spawn in the hell level][username in chat]``` then the codex will automatically add an entry, for example: "Increase difficulty by changing the level to hell". The codex will be applied to all commits, and the service can be used to go back and apply a codex entry to every commit, as long as the tags have been applied.<br>-There is another feature called "merge-o-matic". If you create a pull request automatically for example, to add a single word to the ```username``` tag, for example for example to add a single tag value, for example ```[username][username in chat][username not in chat]```. If the tag has been changed to ```[username not in chat]``` in ```[username in chat]``` then the server will automatically update all of the commits as soon as you apply the change, and auto update the codex. <br>-Another feature called "commit-o-matic" which automatically applies a set of commits to all of the files on the entire server. For example if you change a tag in one file to make it easier to read with an auto ```[hardcore mode][hardcore]``` and you apply the change to a function ```[Roguelike][Roguelike mode][Survival][Survival mode]``` but you also want to apply the change to every other instance of the tag, to ```[rpg][survival]``` or ```[hack and slash][fantasy]``` then the server will automatically apply the change to every commit, even if you already pushed, for example to a public repository.<br>-There is a feature called "toggle-o-matic" which automatically toggles the order of a set of tags. For example if you have two ```[rare items]``` and ```[regular items]``` tags, then the server will automatically toggle the order of the tags in a commit by commit basis. For example if you have two files ```file1.txt``` and ```file2.txt``` and you are working on ```file1.txt``` but you push a commit that has two ```[rare items]``` tags, and meanwhile you have two ```[regular items]``` tags in ```file2.txt``` then the server will automatically toggle the order of the tags in ```file2.txt``` to be ```[rare items ```[regular items]``` ```[regular items]```[rare items]``` or ```[regular ```[rare items]``` ```[regular ```[rare items]``` so that ```file2.txt``` is up-to-date automatically. <br>-There is a feature that automatically converts code to other languages.<br>-There is a feature that automatically creates a gist, for ```open source``` projects. But the gist is non-editable, and is auto-updated whenever there is a commit to the ```master``` branch. You can also create a gist that is updated to the ```HEAD``` of the ```master``` branch. ```HEAD``` is different than ```master``` because it can be ahead of ```master``` by any number of commits. <br>-There is a feature that automatically updates the code to different versions, for example if you have a ```unity 2018``` project but you want to upgrade it to ```unity 2020``` then the service will automatically create the commits, and then automatically create the gist automatically for you. And it will apply the different tags and different codex automatically, for example ```[unity 2020][unity 2020 lts]``` automatically. And it will apply the tags to the auto-generated gist. You can also create a gist with a ```HEAD``` version instead of an ```LTS``` version. For example ```[unity 2020][unity 2020 lts]``` might be ```[unity 2020][unity 2020.3.15f2]``` or for example ```[unity 2020][unity 2020 beta]```.<br>-You can also create a gist that is updated to any version number. For example ```[unity 2020][unity 2020 lts][unity 2018][unity 2018 lts]``` could be a gist that is updated to the latest version of ```2020``` or the latest version of ```2018``` or the latest ```lts``` version of ```2020``` and ```2018``` or the latest ```beta``` version of ```2020``` and ```2018``` or the latest ```alpha``` version of ```2020``` and ```2018``` or the latest ```rc``` version of ```2020``` and ```2018``` or the latest ```experimental``` version of ```2020 ```and ```2018``` or the latest ```dev``` version of ```2020``` and ```2018``` or the latest ```HEAD``` version of ```2020``` and ```2018``` or the latest ```mainline``` version of ```2020``` and ```2018``` automatically. <br>-There is a feature that automatically converts code to different versions of a language, for example if you have ```java 8``` code but you want to update it to ```java 17``` then the service will automatically apply the different tags to create a single commit that updates the code to different versions. So you just right click on the different tags, for example ```[java 8][java 11][java 14][java 15][java 16][java 17][java 8 lts][java 11 lts][java 14 lts][java ```15 lts][java 16 lts][java 17 lts][java 8 dev][java 11 dev][java 14 dev][java 15 dev][java 16 dev][java 17 dev][java 8 ```mainline][java 11 mainline][java 14 mainline][java 15 mainline][java 16 mainline][java 17 mainline][java 8 ```head][java 11 head][java 14 head][java 15 head][java 16 head][java 17 head][java 8 ```experimental][java 11 experimental][java 14 experimental][java 15 experimental][java 16 experimental][java ```17 experimental][java 8 rc][java 11 rc][java 14 rc][java 15 rc][java 16 rc][java 17 rc][java 8 beta][java ```11 beta][java 14 beta][java 15 beta][java 16 beta][java 17 beta][java 8 rc][java 11 rc][java 14 ```rc][java 15 rc][java 16 rc][java 17 rc][java 8 alpha][java 11 alpha][java 14 alpha][java 15 alpha][java 16 ```alpha][java 17 alpha]``` automatically. <br>-There is a feature that automatically converts code to different languages, for ```open source``` projects. Whenever you push a commit, then the server automatically creates a gist for each different language. For example if you push a commit to your ```python``` project, then the server automatically creates a gist for ```python``` ```c#``` ```c``` ```c++ ``` ```rust``` ```go``` ```haskell``` ```lisp``` ```perl``` ```ruby``` ```swift``` ```kotlin``` ```java``` ```javascript``` ```sql``` ```php``` ```scala``` automatically. And then you go to your gist and you go to a page that displays every gist, ```python``` ```c#``` ```c``` ```c++``` ```rust``` ```go``` ```haskell``` ```lisp``` ```perl``` ```ruby``` ```swift``` ```kotlin``` ```java``` ```javascript``` ```sql``` ```php``` ```scala``` like this: gist/python, gist/c#, gist/c, gist/c++, gist/rust, gist/go, gist/haskell, gist/lisp, gist/perl, gist/ruby, gist/swift, gist/kotlin, gist/java, gist/javascript, gist/sql, gist/php, gist/scala. And then you can go to each gist and create a new gist that is updated to the latest ```HEAD``` or ```mainline``` or ```dev``` version of the language. So if you go to the gist/python page, then you can create a new gist called gist/python-head, gist/python-dev, gist/python-mainline. And then the server will automatically update the gist to the automatically updated commit whenever you push a commit. So for example, you push a commit to