0.1.0

⇅ Show all commits (+ initial commit)

Features

Bootstrap based on tmpl-go template repository — #1 (⊶ 8ec80d1) by @svengreb

↠ Bootstrapped the basic project setup, structure and development workflow based on the “tmpl-go“ template repository.

GitHub Health Files: Code Owners — #2 ⇄ #3 (⊶ d76856d) by @svengreb

↠ GitHub introduced the “Code Owners“ feature back in 2017 that allows to define individuals or teams that are responsible for code in a repository. The feature is configured by a codeowners file that must be placed either in the root, /docs or .github directory of an repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

GitHub Health Files: Code Of Conduct — #4 ⇄ #5 (⊶ 80e79e4) by @svengreb

↠ As part of the community health files, a code of conduct to define community standards, signal a welcoming and inclusive project, and outline procedures for handling abuse has been created.
The feature is configured by a code_of_conduct.md file that must be placed either in the root, /docs or .github directory of an repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

GitHub Health Files: Contributing — #6 ⇄ #7 (⊶ 564cf31) by @svengreb

↠ As part of the community health files, the contribution guidelines to communicate to project/repository contributors have been created.
The feature is configured by a contributing.md file that must be placed either in the root, /docs or .github directory of an repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

GitHub Health Files: Security Policy — #8 ⇄ #9 (⊶ 6361143) by @svengreb

↠ As part of the community health files, a security policy to give instructions for how to report a security vulnerability the project has been created.
The feature is configured by a security.md file that must be placed either in the root, /docs or .github directory of an repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

GitHub Health Files: Sponsors (Funding) — #10 ⇄ #11 (⊶ aaf12fa) by @svengreb

↠ As part of the community health files, the GitHub sponsors configuration file has been added to display a sponsor button in an repository.
The feature is configured by the funding.yml file that must be placed either in the root, /docs or .github directory of an repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

GitHub Health Files: Issue Template Chooser — #12 ⇄ #13 (⊶ d40c313) by @svengreb

↠ As part of the community health files, the issue template chooser configuration file to customize the issue template chooser that is shown when creating a new issue in a repository.
The feature is configured by the issue_template/config.yml file that must be placed either in the root, /docs or .github directory of a repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

GitHub Health Files: Support Resources — #14 ⇄ #15 (⊶ cb3760c) by @svengreb

↠ As part of the community health files, the support resources file to provide instructions for how to ask for help and general Nord community & support resources.
The feature is configured by the support.md file that must be placed either in the root, /docs or .github directory of a repository.

For Nord this file is provided globally by this organization‘s .github repository for all repositories that do not require a specific or special configuration.

Document repository content — #16 ⇄ #17 (⊶ 638aa46) by @svengreb

↠ To describe the purpose of this repository, the content has been documented in the repository‘s README.

The full changelog is available in the repository

Copyright © 2016-present Sven Greb