[#] Stop using obsolete .github directory

This commit is a part of multi-repo cleanup effort:
TrueCloudLab/frostfs-infra#136

Signed-off-by: Vitaliy Potyarkin <v.potyarkin@yadro.com>

.github/CODEOWNERS

@@ -1 +0,0 @@
-*   @alexvanin @realloc @fyrchik @anatoly-bogatyrev

.github/workflows/buf.yml

@@ -1,36 +0,0 @@
-name: Buf lint
-
-on:
-  pull_request:
-    branches:
-      - master
-
-jobs:
-  lint:
-    runs-on: ubuntu-20.04
-    steps:
-      - uses: actions/checkout@v2
-      - uses: wizhi/setup-buf@v1
-        with:
-          version: 0.20.5
-      - run: buf check lint
-
-  breaking:
-    runs-on: ubuntu-20.04
-    steps:
-      - name: Setup buf
-        uses: wizhi/setup-buf@v1
-        with:
-          version: 0.20.5
-      - name: Check out ref code
-        uses: actions/checkout@v2
-        with:
-          ref: ${{ github.base_ref }}
-          path: baseref
-      - run: cd baseref && buf image build -o image.bin
-
-      - name: Check out code
-        uses: actions/checkout@v2
-        with:
-          path: prclone
-      - run: cd prclone && buf check breaking --against-input ../baseref/image.bin

.github/workflows/dco.yml

@@ -1,21 +0,0 @@
-name: DCO check
-
-on:
-  pull_request:
-    branches:
-      - master
-
-jobs:
-  commits_check_job:
-    runs-on: ubuntu-latest
-    name: Commits Check
-    steps:
-    - name: Get PR Commits
-      id: 'get-pr-commits'
-      uses: tim-actions/get-pr-commits@master
-      with:
-        token: ${{ secrets.GITHUB_TOKEN }}
-    - name: DCO Check
-      uses: tim-actions/dco@master
-      with:
-        commits: ${{ steps.get-pr-commits.outputs.commits }}

CODEOWNERS

@@ -0,0 +1 @@
+.*   @alexvanin @realloc @fyrchik @a.bogatyrev

CONTRIBUTING.md

@@ -87,7 +87,7 @@ $ git push origin feature/123-something_awesome
 ```
 
 ### Create a Pull Request
-Pull requests can be created via GitHub. Refer to [this
+Pull requests can be created via git.frostfs.info. Refer to [this
 document](https://help.github.com/articles/creating-a-pull-request/) for
 detailed steps on how to create a pull request. After a Pull Request gets peer
 reviewed and approved, it will be merged.

Makefile

@@ -10,7 +10,7 @@ doc:
 	@for f in `find . -type f -name '*.proto' -exec dirname {} \; | sort -u `; do \
 		echo "⇒ Documentation for $$(basename $$f)"; \
 		protoc \
-			--doc_opt=.github/markdown.tmpl,$${f}.md \
+			--doc_opt=.forgejo/markdown.tmpl,$${f}.md \
 			--proto_path=.:/usr/local/include \
 			--doc_out=proto-docs/ $${f}/*.proto; \
 	done

README.md

@@ -1,5 +1,5 @@
 <p align="center">
-<img src="./.github/logo.svg" width="500px" alt="FrostFS">
+<img src="./.forgejo/logo.svg" width="500px" alt="FrostFS">
 </p>
 <p align="center">
   <a href="https://frostfs.info">FrostFS</a> API language-agnostic protocol definitions

doc/release_instructions.md

@@ -20,7 +20,7 @@ Add an entry to the CHANGELOG.md following the style established there.
 Add a codename for releases with the new major version, version and release date in
 the heading. Write a paragraph describing the most significant changes done in
 this release. Then add sections with what has been added, changed and removed,
-describing each change briefly with a reference to GitHub issues, where
+describing each change briefly with a reference to issues, where
 available.
 
 ## Release commit
@@ -38,7 +38,7 @@ Release v2.9.0 - Anmyeondo (안면도, 安眠島)
 Use `vX.Y.Z` tag following the semantic versioning standard. For pre-release
 versions use `vX.Y.Z-rc.N` scheme.
 
-## Push changes and release tag to Github
+## Push changes and release tag to repository
 
 This step should bypass the default PR mechanism to get a correct result (so
 that releasing requires admin privileges for the project), both the `master`
@@ -48,9 +48,9 @@ branch update and tag must be pushed simultaneously like this:
 $ git push origin master v2.7.0
 ```
 
-## Make a proper Github release
+## Make a proper release
 
-Edit an automatically-created release on Github.
+Edit an automatically-created release on git.frostfs.info
 
 Release title has to follow `<version> <Romanized codename> (<Hangeul, Hanja
 codename> )` scheme for major releases and just `<version>` for regular point
@@ -58,5 +58,5 @@ releases.
 
 ## Post-release actions
 
-* Close corresponding X.Y.Z Github milestone
+* Close corresponding X.Y.Z milestone
 * Make announcements in Matrix and Discord channels