fix: issues

Author: gilescope

.github/linters/.markdown-lint.yml

@@ -1,3 +1,3 @@
+MD013: false  # line length 80
 MD026: false
 MD034: false
-

.github/workflows/ci.yaml

@@ -8,9 +8,10 @@ permissions:
 # Run on pushes to any branch and pull requests
 on:
   push:
-    branches-ignore: ['main']
-  pull_request:
     branches: ['main']
+  pull_request:
+    branches: ['**']
+
 jobs:
   # Lint all YAML, JSON & Shell
   lint:
@@ -29,7 +30,10 @@ jobs:
           VALIDATE_YAML: true
           VALIDATE_JSON: true
           VALIDATE_SHELL: true
-          FILTER_REGEX_EXCLUDE: ^cardano-config/
+
+          VALIDATE_MARKDOWN_PRETTIER: false
+          VALIDATE_YAML_PRETTIER: false
+          FILTER_REGEX_EXCLUDE: (^cardano-config/|LICENSE\.md)
         env:
           # tell it your default branch so it can diff
           DEFAULT_BRANCH: origin/main

CODE_OF_CONDUCT.md

@@ -1,7 +1,9 @@
 # Our Pledge
+
 In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ## Our Standards
+
 Examples of behavior that contributes to creating a positive environment include:
 
 - Using welcoming and inclusive language
@@ -12,25 +14,30 @@ Examples of behavior that contributes to creating a positive environment include
 
 Examples of unacceptable behavior by participants include:
 
--The use of sexualized language or imagery and unwelcome sexual attention or advances
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
 - Trolling, insulting/derogatory comments, and personal or political attacks
 - Public or private harassment
 - Publishing others’ private information, such as a physical or electronic address, without explicit permission
 - Other conduct which could reasonably be considered inappropriate in a professional setting
+
 ## Our Responsibilities
+
 Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
 Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ## Scope
+
 This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
 ## Enforcement
+
 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at legal@midnight.foundation. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.
 
 ## Attribution
+
 This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
 
 For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq

README.md

@@ -19,23 +19,27 @@ This allows for easy orchestration of the Midnight Node service.
 The `.envrc` file will automatically create a random private key and save it as `midnight-node.privatekey`.
 
 Choose which compose files to use:
+
 - `compose.yml` for Midnight Node
 - `compose-partner-chains.yml` for Cardano + DB Sync
 - `proof-server.yml` for Local Proof Server
 
 One can use one or multiple compose files at once.
 
 For example, to run the Midnight Node, you can do:
+
 ```shell
 docker compose up -d
 ```
 
 or to run the Midnight Node and Cardano DB Sync, you can do:
+
 ```shell
 docker compose -f ./compose-partner-chains.yml -f ./compose.yml up -d
 ```
 
 or to run the Midnight Node, Cardano DB Sync and a local Proof Server, you can do:
+
 ```shell
 docker compose -f ./compose-partner-chains.yml -f ./compose.yml -f ./proof-server.yml up -d
 ```

SECURITY.md

@@ -13,7 +13,7 @@ for Linux Foundation projects.
 
 The Midnight foundation takes all security issues seriously, which includes all source code repositories managed
 through our [GitHub organization](https://github.com/midnightntwrk). If you believe you have found a security vulnerability in any Midnight Foundation
-owned repository, <B>please report it using GitHub's private vulnerability reporting</B> and not through public GitHub issues. To learn more about GitHub's
+owned repository, *please report it using GitHub's private vulnerability reporting* and not through public GitHub issues. To learn more about GitHub's
 private vulnerability reporting and how to submit a vulnerability report, please review [GitHub's documentation on private reporting](https://docs.github.com/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability).
 
 Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
@@ -43,7 +43,6 @@ for additional information or guidance.
 Thank you for improving the security of Midnight. We appreciate your dedication to responsible disclosure and will
 make every effort to acknowledge your contributions.
 
-
 ## Vulnerability management
 
 When the maintainers receive a disclosure report, they will assign it to a