Improvements for release process (#96)

* Improvements for release process

### What's done:
* Added RELEASING.md
* Modified pull_request_template.md

.github/PULL_REQUEST_TEMPLATE/rule.md → .github/pull_request_template.md

@@ -1,13 +1,14 @@
 ## Which rule and warnings did you add?
 
+This pull request closes <!-- insert related issue number -->
 <!-- Briefly describe rule and warnings -->
 
 ## Actions checklist
 * [ ] Implemented Rule, added Warnings
 * [ ] Added tests on checks
 * [ ] Added tests on fixers
 * [ ] Updated rules-config.json
-* [ ] Updated Readme
+* [ ] Updated available-rules.md
 
 ## Fixme
 

RELEASING.md

@@ -0,0 +1,13 @@
+# How to release a new version of diKTat
+
+* You should have permissions to push to the main repo
+* Simply create a new git tag with format `v*` and push it. Github workflow will perform release automatically.
+
+  For example:
+  ```bash
+  $ git tag v1.0.0
+  $ git push origin --tags 
+  ```
+
+After the release workflow has started, version number is determined from tag. Binaries are uploaded to maven repo and 
+a new github release is created with fat jar.

pom.xml

@@ -143,12 +143,14 @@
         </snapshotRepository>
     </distributionManagement>
     <repositories>
+        <!-- this is needed to use ktlint 0.37.1-fork -->
         <repository>
             <id>artipie</id>
             <url>https://central.artipie.com/akuleshov7/diktat</url>
         </repository>
     </repositories>
     <pluginRepositories>
+        <!-- this is needed to use forked ktlint and diktat inside antrun plugin -->
         <pluginRepository>
             <id>artipie</id>
             <url>https://central.artipie.com/akuleshov7/diktat</url>