Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Initial repository clean up for Go rewrite #49

Closed
8 tasks done
arcticicestudio opened this issue Jun 22, 2019 · 0 comments
Closed
8 tasks done

Initial repository clean up for Go rewrite #49

arcticicestudio opened this issue Jun 22, 2019 · 0 comments
Labels
context-workflow scope-maintainability type-task
Milestone
0.4.0

Comments

@arcticicestudio
Copy link
Owner

arcticicestudio commented Jun 22, 2019 •
edited
Loading

Epic: #33
Blocks #34 #35 #36 #37 #38 #39 #42 #43 #44 #45 #46 #47 #48

In order to start the Go project rewrite from scratch the current repository structure and files should be reset to a clean state to remove all references to the previous implementations, documentations and project structure/layout.

Starting from a „fresh“ state allows to build the project up with the correct structure and design pattern as if there were leftovers from the previous repository data resulting in mixed files and folders.

This ticket must be resolved first before all other tickets also bound to the epic #33!
See the corresponding milestone for more details about the implementation/resolve order.

Tasks

  • .idea/ — Delete the whole folder, the files are scoped for Pycharm Community Edition and will be replaced with the correct files for IntelliJ Ultimate Edition with the official Go plugin (Goland) later on.
  • assets/ — Delete the whole folder, all assets will be redesigned and added again later on.
  • bin/ — Delete the whole folder, the script is part of the Python implementation and represented the entry point of the app.
  • snowsaw/ — Delete the whole folder, includes the main Python app and API implementations.
  • .editorconfig — Delete the file, it will be recreated in EditorConfig #38 to match the new project layout and latest Arctic Ice Studio style guides.
  • .gitignore — Delete the file, it will be recreated in Git ignore and attribute pattern #35 to match the new project layout and latest Arctic Ice Studio project design standards/guidelines.
  • CHANGELOG.md — Delete the file, it will be recreated later on to match the new project layout and latest Arctic Ice Studio project design standards/guidelines.
  • README.md — Delete the file, it will be recreated later on to match the new project layout and latest Arctic Ice Studio project design standards/guidelines including the new project assets (logo, repository hero etc.).
@arcticicestudio arcticicestudio added this to the 0.4.0 milestone Jun 22, 2019
@arcticicestudio arcticicestudio self-assigned this Jun 22, 2019
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Initial repository clean up for Go rewrite
b311c41 
In order to start the Go project rewrite (1) from scratch the current
repository structure and files have been reset to a clean state to
remove all references to the previous implementations, documentations
and project structure/layout.

Starting from a "fresh" state allows to build the project up with the
correct structure and design pattern as if there were leftovers from
the previous repository data resulting in mixed files and folders.

This commit must be pushed first before all other blocked tickets can be
resolved that are also bound to the epic GH-33!
See the corresponding milestone (2) for more details about the
implementation/resolve order.

>>>> Tasks

- `.idea/` (3) - Deleted the whole folder, the files were scoped for
  "Pycharm Community Edition" and will be replaced with the correct
  files for "IntelliJ Ultimate Edition" with the official Go plugin (4)
  (Goland (5)) later on.
- `assets/` (6) - Deleted the whole folder, all assets will be
  redesigned and added again later on.
- `bin/` (7) - Deleted the whole folder, the script was part of the
  Python implementation and represented the entry point of the app.
- `snowsaw/` (8) - Deleted the whole folder, included the main Python
  app and API implementations.
- `.editorconfig` (9) - Deleted the file, it will be recreated in GH-38
  to match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines.
- `.gitignore` (10) - Deleted the file, it will be recreated in GH-35 to
  match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines.
- `CHANGELOG.md` (11) - Deleted the file, it will be recreated later on to
  match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines.
- `README.md` (12) - Deleted the file, it will be recreated later on to
  match the new project layout and latest "Arctic Ice Studio" project
  design standards/guidelines including the new project assets
  (logo, repository hero etc.).

References:
  (1) #33
  (2) https://github.com/arcticicestudio/snowsaw/milestone/5
  (3) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/.idea
  (4) https://plugins.jetbrains.com/plugin/9568-go
  (5) https://www.jetbrains.com/go
  (6) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/assets
  (7) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/bin
  (8) https://github.com/arcticicestudio/snowsaw/tree/bc54e5136be27f8037de5bbc2f046f37eb036274/snowsaw
  (9) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/.editorconfig
  (10) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/.gitignore
  (11) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/CHANGELOG.md
  (12) https://github.com/arcticicestudio/snowsaw/blob/bc54e5136be27f8037de5bbc2f046f37eb036274/README.md

Epic: GH-33
Blocked GH-34 GH-35 GH-36 GH-37 GH-38 GH-39 GH-42 GH-43 GH-44 GH-45
        GH-46 GH-47 GH-48
Resolves GH-49
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Merged
@arcticicestudio arcticicestudio removed their assignment Jun 22, 2019
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
MIT license
47ea77b 
Added the `LICENSE.md` file for the MIT license (1).

References:
  (1) https://opensource.org/licenses/MIT

Epic: GH-33
Depends on GH-49
GH-49
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
MIT license
015227e 
Added the `LICENSE.md` file for the MIT license (1).

References:
  (1) https://opensource.org/licenses/MIT

Epic: GH-33
Depends on GH-49
GH-34
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
MIT license (#51)
8093595 
Added the `LICENSE.md` file for the MIT license (1).

References:
  (1) https://opensource.org/licenses/MIT

Epic: GH-33
Depends on GH-49
GH-34
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Add Git ignore and attribute pattern
329a754 
Added the `.gitattributes` (1) and `.gitignore` (2) configuration files
for pattern handling that are matching the latest "Arctic Ice Studio"
project design standards/guidelines.

References:
  (1) https://git-scm.com/docs/gitattributes
  (2) https://git-scm.com/docs/gitignore

Epic: GH-33
Blocks GH-48
Depends on GH-49
Resolves GH-35
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Add Git mail mapping
162057c 
Added a Git mailmap (1) file to link to in documentations to allow
contributors to send mails regarding security issues. This prevents
unnecessary overhead of updating all documents when new core team and
members and contributors are added and additionally adds the main
functionality of the file:
Mapping commits when someone uses a different email address.

References:
  (1) https://git-scm.com/docs/git-shortlog#_mapping_authors

Epic: GH-33
Depends on GH-49
Resolves GH-46
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
GitHub code owners
934bdac 
The project adapted to GitHub's code owners  feature. This allows to
define matching pattern for project paths to automatically add all
required reviewers of the core team and contributors to new PRs.

See GitHub Help (2) for more details.

References:
  (1) https://github.com/blog/2392-introducing-code-owners
  (2) https://help.github.com/articles/about-codeowners

Epic: GH-33
Depends on GH-49
Resolves GH-43
This was referenced Jun 22, 2019
Closed
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Open Source community standards: Code of Conduct
51346eb 
To facilitate a healthy and constructive community behavior, snowsaw
adheres and enforce a code of conduct (1).

This commit includes the sections about

- what we believe in and how we act
- unacceptable behavior
- the responsibilities of the maintainer
- the enforcement of the Code of Conduct
- consequences for violations
- the scope of the Code of Conduct

See the GitHub Help (2) for more details about the provided
integrations.

References:
  (1) opensource.guide/code-of-conduct
  (2) help.github.com/articles/adding-a-code-of-conduct-to-your-project

Epic: GH-33
Depends on GH-49
GH-39
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Open Source community standards: Contributing Guidelines
0a72f8d 
The contribution guidelines (1) help to build a community that
encourages people to use, contribute to (2), and evangelize a project.

It includes sections about

- how to get started
- bug reports
- enhancement suggestions
- pull requests
- style guides
  -  Markdown Style Guide (3)
  - Git Style Guide (4)
- credits

See the GitHub introduction blog post (5) and GitHub Help (6) for more
details about the provided integrations.

References:
  (1) github.com/blog/1184-contributing-guidelines
  (2) opensource.guide/how-to-contribute
  (3) arcticicestudio/styleguide-markdown
  (4) arcticicestudio/styleguide-git
  (5) https://github.blog/2012-09-17-contributing-guidelines
  (5) help.github.com/articles/setting-guidelines-for-repository-contributors

Epic: GH-33
Depends on GH-49
Resolves GH-39
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
GitHub Open Source Community Standards (#52)
30df86d 
* Open Source community standards: Code of Conduct

To facilitate a healthy and constructive community behavior, snowsaw
adheres and enforce a code of conduct (1).

This commit includes the sections about

- what we believe in and how we act
- unacceptable behavior
- the responsibilities of the maintainer
- the enforcement of the Code of Conduct
- consequences for violations
- the scope of the Code of Conduct

See the GitHub Help (2) for more details about the provided
integrations.

References:
  (1) opensource.guide/code-of-conduct
  (2) help.github.com/articles/adding-a-code-of-conduct-to-your-project

Epic: GH-33
Depends on GH-49
GH-39

+---------------------------------------------------------------------+

* Open Source community standards: Contributing Guidelines

The contribution guidelines (1) help to build a community that
encourages people to use, contribute to (2), and evangelize a project.

It includes sections about

- how to get started
- bug reports
- enhancement suggestions
- pull requests
- style guides
  -  Markdown Style Guide (3)
  - Git Style Guide (4)
- credits

See the GitHub introduction blog post (5) and GitHub Help (6) for more
details about the provided integrations.

References:
  (1) github.com/blog/1184-contributing-guidelines
  (2) opensource.guide/how-to-contribute
  (3) arcticicestudio/styleguide-markdown
  (4) arcticicestudio/styleguide-git
  (5) https://github.blog/2012-09-17-contributing-guidelines
  (5) help.github.com/articles/setting-guidelines-for-repository-contributors

Epic: GH-33
Depends on GH-49
Resolves GH-39
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
GitHub issue templates
84ef4a9 
This commit makes use of GitHub's feature to define multiple issue
templates (1). The initial template file that has been used when the
feature was introduced (2) and is now used as a fallback/generic
template to redirect to one of the other specific templates.
The UI helps users to open a new issue in projects by prompting them to
choose from multiple issue types.

References:
  (1) blog.github.com/2018-01-25-multiple-issue-and-pull-request-templates
  (2) blog.github.com/2016-02-17-issue-and-pull-request-templates

Epic: GH-33
Depends on GH-49
GH-42
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
GitHub pull request template
a55d014 
This commit makes use of GitHub's feature to define multiple pull
request templates (1). See the GitHub Help (2) for more details about
issue and pull request templates.

References:
  (1) blog.github.com/2016-02-17-issue-and-pull-request-templates
  (2) help.github.com/articles/about-issue-and-pull-request-templates

Epic: GH-33
Depends on GH-49
Resolves GH-42
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
GitHub issue and pull request templates (#53)
0213c4e 
* GitHub issue templates

This commit makes use of GitHub's feature to define multiple issue
templates (1). The initial template file that has been used when the
feature was introduced (2) and is now used as a fallback/generic
template to redirect to one of the other specific templates.
The UI helps users to open a new issue in projects by prompting them to
choose from multiple issue types.

References:
  (1) blog.github.com/2018-01-25-multiple-issue-and-pull-request-templates
  (2) blog.github.com/2016-02-17-issue-and-pull-request-templates

Epic: GH-33
Depends on GH-49
GH-42

<--------------------------------------------------------------------->

* GitHub pull request template

This commit makes use of GitHub's feature to define multiple pull
request templates (1). See the GitHub Help (2) for more details about
issue and pull request templates.

References:
  (1) blog.github.com/2016-02-17-issue-and-pull-request-templates
  (2) help.github.com/articles/about-issue-and-pull-request-templates

Epic: GH-33
Depends on GH-49
Resolves GH-42
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
EditorConfig
26a6347 
Added the EditorConfig (1) file that matches "Arctic Ice Studio's" style
guides for a consistent code base between different editors and IDEs.

References:
  (1) https://editorconfig.org

Epic: GH-33
Depends on GH-49
Resolves GH-38
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
NPM project-level configuration file
7a6fdd3 
Added the NPM `.npmrc` (1) configuration file to ensure specific
configurations are set project-wide for all core team members and
contributors. This includes the usage of the lockfile
(`package-lock.json`) (2) and exact (dev)dependency package versions.

References:
  (1) https://docs.npmjs.com/files/npmrc
  (2) https://docs.npmjs.com/files/package-locks

Epic: GH-33
Depends on GH-49
Blocks GH-36 GH-37 GH-44 GH-45
Resolves GH-47
This was referenced Jun 22, 2019
Closed
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Install remark-cli and remark-preset-lint-arcticicestudio NPM pkgs.
0b72c39 
Installed remark-lint (1) through `remark-cli` (2) using the
`remark-preset-lint-arcticicestudio` (3) preset that implements the
"Arctic ice Studio" Markdown Style Guide (4).

Also updated the Git ignore pattern to handle "Node.js" data.

References:
  (1) remarkjs/remark-lint
  (2) npmjs.com/package/remark-cli
  (3) arcticicestudio/remark-preset-lint-arcticicestudio
  (4) arcticicestudio.github.io/styleguide-markdown

Epic: GH-33
Depends on GH-47 GH-49
GH-36
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Implement remark config and ignore pattern file
4190205 
Created the main remark (1) configuration file and initially set up the
`remark-preset-lint-arcticicestudio` (2) preset.
Also added the `.remarkignore` file with to define ignore pattern.

References:
  (1) remark.js.org
  (2) remarkjs/remark-lint
  (3) arcticicestudio/remark-preset-lint-arcticicestudio

Epic: GH-33
Depends on GH-47 GH-49
GH-36
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Implement NPM script/task to lint Markdown files
74765a0 
The NPM scripts/tasks allow to run the Markdown linting separately and
as well as running the all `lint` task together.

Also added the `npm-run-all` package that simplifies the paralell and
serial execution of multiple NPM scripts/tasks including name wildcard
support.

Epic: GH-33
Depends on GH-47 GH-49
GH-36
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
remark-lint (#54)
acd0df4 
* Install `remark-cli` and `remark-preset-lint-arcticicestudio` NPM pkgs.

Installed remark-lint (1) through `remark-cli` (2) using the
`remark-preset-lint-arcticicestudio` (3) preset that implements the
"Arctic ice Studio" Markdown Style Guide (4).

Also updated the Git ignore pattern to handle "Node.js" data.

References:
  (1) remarkjs/remark-lint
  (2) npmjs.com/package/remark-cli
  (3) arcticicestudio/remark-preset-lint-arcticicestudio
  (4) arcticicestudio.github.io/styleguide-markdown

Epic: GH-33
Depends on GH-47 GH-49
GH-36

<--------------------------------------------------------------------->

* Implement remark config and ignore pattern file

Created the main remark (1) configuration file and initially set up the
`remark-preset-lint-arcticicestudio` (2) preset.
Also added the `.remarkignore` file with to define ignore pattern.

References:
  (1) remark.js.org
  (2) remarkjs/remark-lint
  (3) arcticicestudio/remark-preset-lint-arcticicestudio

Epic: GH-33
Depends on GH-47 GH-49
GH-36

<--------------------------------------------------------------------->

* Implement NPM script/task to lint Markdown files

The NPM scripts/tasks allow to run the Markdown linting separately and
as well as running the all `lint` task together.

Also added the `npm-run-all` package that simplifies the paralell and
serial execution of multiple NPM scripts/tasks including name wildcard
support.

Epic: GH-33
Depends on GH-47 GH-49
GH-36
This was referenced Jun 22, 2019
Closed
Closed
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Install prettier
fc70c6e 
Installed the main `prettier` (1) NPM package.

References:
  (1) npmjs.com/package/prettier

Epic: GH-33
Depends on GH-47 GH-49
GH-37
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Implement Prettier configuration and ignore pattern file
d8eefc0 
This is one of the main features of Prettier: It already provides the
best and recommended style configurations of-out-the-box.
The only option that has been changed is the print width (1). It is set
to `80` by default which not up-to-date for modern screens (might only
be relevant when working in terminals only like e.g. with Vim). It is
now set to `120` used by all of Arctic Ice Studio's style guides.
The `prettier.config.js` configuration file is placed in the project
root as well as the `.prettierignore` file that defines ignore pattern.

References:
  (1) prettier.io/docs/en/options.html#print-width

Epic: GH-33
Depends on GH-47 GH-49
GH-37
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Implement NPM format:pretty script/task for Prettier
87bfb7d 
To allow to format all sources the `format:pretty` NPM script/task has
been added as well as the `format` script/task to run all tasks of the
formatting workflow.

Epic: GH-33
Depends on GH-47 GH-49
Resolves GH-37
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Prettier (#55)
be3e59a 
* Install `prettier`

Installed the main `prettier` (1) NPM package.

References:
  (1) npmjs.com/package/prettier

Epic: GH-33
Depends on GH-47 GH-49
GH-37

<--------------------------------------------------------------------->

* Implement Prettier configuration and ignore pattern file

This is one of the main features of Prettier: It already provides the
best and recommended style configurations of-out-the-box.
The only option that has been changed is the print width (1). It is set
to `80` by default which not up-to-date for modern screens (might only
be relevant when working in terminals only like e.g. with Vim). It is
now set to `120` used by all of Arctic Ice Studio's style guides.
The `prettier.config.js` configuration file is placed in the project
root as well as the `.prettierignore` file that defines ignore pattern.

References:
  (1) prettier.io/docs/en/options.html#print-width

Epic: GH-33
Depends on GH-47 GH-49
GH-37


* Implement NPM `format:pretty` script/task for Prettier

To allow to format all sources the `format:pretty` NPM script/task has
been added as well as the `format` script/task to run all tasks of the
formatting workflow.

Epic: GH-33
Depends on GH-47 GH-49
Resolves GH-37
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Install and configure lint-staged
2696968 
Installed `lint-staged` (1) to run linters against staged Git files to
prevent to add code that violates any style guide into the code base.

The `lint-staged.config.js` configuration file has been placed in
the project root and includes the commands that should be run for
matching file extensions (globs). It includes at least the three
following entries with the same order as listed here:

1. `prettier --list-different` - Run Prettier (GH-37) against
  `*.{js,json,md,yml}` to ensure all files are formatted correctly.
  The `--list-different` prints the found files that are not conform to
  the Prettier configuration.
2. `remark --no-stdout` - Run remark-lint (GH-36) against `*.md` to
  ensure all Markdown files are compliant to the style guide
   The `--no-stdout` flag suppresses the output of the parsed file
   content.

References:
  (1) https://github.com/okonet/lint-staged

Epic: GH-33
Depends on GH-36 GH-37 GH-47 GH-49
Blocks GH-45
Resolves GH-44
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
2 tasks
arcticicestudio added a commit that referenced this issue Jun 22, 2019
@arcticicestudio
Install and configure husky
955cd7c 
Installed Husky (1), the tool that make Git hooks easy and can prevent
bad Git commits, pushes and more!

The `.huskyrc.js` configuration file is placed in the project root and
includes the commands to run for any supported Git hook (1). This
commit initially adds configs for the following hook(s):

- `pre-commit` - Run lint-staged (GH-44) before each commit (via
  `lint-staged` command) to ensure all staged files are compliant to
  all style guides.

References:
  (1) https://github.com/typicode/husky
  (2) https://github.com/typicode/husky/blob/master/DOCS.md#supported-hooks

Epic: GH-33
Depends on GH-4 GH-47 GH-49
Resolves GH-45
@arcticicestudio arcticicestudio mentioned this issue Jun 22, 2019
Closed
7 tasks
arcticicestudio added a commit that referenced this issue Jun 23, 2019
@arcticicestudio
Configure Git attributes filter and diff to use git-crypt setup
992dca0 
Ensured to exclude Git specific `.gitattributes` and `.gitignore` files.

Epic GH-33
Depends on GH-35 GH-49
GH-48
arcticicestudio added a commit that referenced this issue Jun 23, 2019
@arcticicestudio
Import trusted GPG keys for git-crypt
d45bc86 
Initialized git-crypt for the repository with `git-crypt init`.

Added GPG keys of all core team members by running the
`git-crypt add-gpg-user --trusted --no-commit <ID>` command where
`--no-commit` flag prevents automatic commit of generated files while
`--trusted` assumes the GPG user IDs are trusted.

Epic GH-33
Depends on GH-35 GH-49
GH-48
arcticicestudio added a commit that referenced this issue Jun 23, 2019
@arcticicestudio
Import trusted GPG keys for git-crypt
a441a1e 
Initialized git-crypt for the repository with `git-crypt init`.

Added GPG keys of all core team members by running the
`git-crypt add-gpg-user --trusted --no-commit <ID>` command where
`--no-commit` flag prevents automatic commit of generated files while
`--trusted` assumes the GPG user IDs are trusted.

Epic GH-33
Depends on GH-35 GH-49
Resolves GH-48
arcticicestudio added a commit that referenced this issue Jun 23, 2019
@arcticicestudio
git-crypt (#56)
3f221b6 
* Configure Git attributes `filter` and `diff` to use `git-crypt` setup

Ensured to exclude Git specific `.gitattributes` and `.gitignore` files.

Epic GH-33
Depends on GH-35 GH-49
GH-48

<--------------------------------------------------------------------->

* Import trusted GPG keys for git-crypt

Initialized git-crypt for the repository with `git-crypt init`.

Added GPG keys of all core team members by running the
`git-crypt add-gpg-user --trusted --no-commit <ID>` command where
`--no-commit` flag prevents automatic commit of generated files while
`--trusted` assumes the GPG user IDs are trusted.

Epic GH-33
Depends on GH-35 GH-49
Resolves GH-48
@arcticicestudio arcticicestudio mentioned this issue Jun 23, 2019
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
context-workflow scope-maintainability type-task
Projects
None yet
Milestone
0.4.0
Development

No branches or pull requests
1 participant
@arcticicestudio