Merge pull request #1 from serokell/gromak/init-repo

[EDNA-4] Init repo

.buildkite/check-trailing-whitespace.sh

@@ -0,0 +1,10 @@
+#!/usr/bin/env bash
+
+files=$(git ls-files -- . | xargs grep --exclude 'LICENSES/*' --exclude '*.patch' --files-with-matches --binary-files=without-match '[[:blank:]]$')
+if [[ ! -z $files ]];then
+ echo ' Files with trailing whitespace found:'
+ for f in "${files[@]}"; do
+ echo " * $f"
+ done
+ exit 1
+fi

.buildkite/pipeline.yml

@@ -0,0 +1,4 @@
+steps:
+ - label: check trailing whitespace
+ commands:
+ - .buildkite/check-trailing-whitespace.sh

.github/pull_request_template.md

@@ -1,11 +1,3 @@
-[//]: # (This is a template of a pull request template.)
-[//]: # (You should modify it considering specifics of a particular repository and put it there.)
-[//]: # (Comments like this are meta-comments, they shouldn't be present in the final template.)
-[//]: # (Comments starting with '<!---' are intended to stay in the final template.)
-
-[//]: # (Keep in mind that it's only a template which contains items relevant to almost all conceivable repository.)
-[//]: # (There can be other important items relevant to your repository that you can add here.)
-
 ## Description
 
 <!--
@@ -14,11 +6,6 @@ further subdivide this into a section describing the problem you are solving and
 another describing your solution.
 -->
 
-[//]: # (Here you can add a link to the corresponding issue tracker, e. g. https://issues.serokell.io/issue/AD-)
-[//]: # (For GitHub/GitLab issues it is better to use just hash symbol or exclamation mark as it is more resistant to repo movements)
-[//]: # (In this case please also prefix the link with "Resolves" keyword)
-[//]: # (See https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-[//]: # (See https://help.github.com/en/github/managing-your-work-on-github/closing-issues-using-keywords)
 ## Related issue(s)
 
 <!--
@@ -29,6 +16,8 @@ For example
 Write 'None' if there are no related issues (which is discouraged).
 -->
 
+https://issues.serokell.io/issue/EDNA-
+
 ## :white_check_mark: Checklist for your Pull Request
 
 <!--
@@ -48,24 +37,11 @@ you must be able to justify that.
  - [ ] If I fixed a bug, I added a regression test to prevent the bug from
  silently reappearing again.
 
-[//]: # (Add more docs here if you have them in the repository)
 - Documentation
  - [ ] I checked whether I should update the docs and did so if necessary:
  - [README](../tree/master/README.md)
- - Haddock
-
-[//]: # (Mostly for public repositories)
-[//]: # (Recording changes is optional, depends on repository, useful for some libs)
-- Public contracts
- - [ ] Any modifications of public contracts comply with the [Evolution
- of Public Contracts](https://www.notion.so/serokell/Evolution-of-Public-Contracts-2a3bf7971abe4806a24f63c84e7076c5) policy.
- - [ ] I added an entry to the [changelog](../tree/master/CHANGES.md) if my changes are visible to the users
- and
- - [ ] provided a migration guide for breaking changes if possible
 
 #### Stylistic guide (mandatory)
 
-[//]: # (Update link to style guide if necesary or remove if it's not present)
-
-- [ ] My commits comply with [the policy used in Serokell](https://www.notion.so/serokell/Where-and-how-to-commit-your-work-58f8973a4b3142c8abbd2e6fd5b3a08e).
+- [ ] My commits comply with [the policy used in Serokell](https://www.notion.so/serokell/Commit-and-PR-policy-4cf98e1a910a415d86b5f2491d9af1af).
 - [ ] My code complies with the [style guide](../tree/master/docs/code-style.md).