Page History

• DCO (required)

• Linters

• Unit tests

• Integration tests

• Code coverage

• Documentation

Example - ReadTheDocs webhook:

https://docs.readthedocs.io/en/stable/integrations.html

• Static analysis aka Static Application Security Testing (SAST)

Example - CodeQL:

https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-with-codeql

Example - Snyk:

https://docs.snyk.io/integrations/git-repository-scm-integrations/github-integration

• Software Composition Analysis dependency scans
• And/or setup Dependabot in Settings/Security

Dependabot:

https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates

Trivy: 

https://github.com/aquasecurity/trivy

It supports pom.xml files but not build.gradle files. If you have a Gradle project you can use the Maven Publish Gradle plugin to generate an equivalent pom.xml file.

• Note: use Reusable github GitHub actions to reduce the number of top-level checks

https://docs.github.com/en/actions/using-workflows/reusing-workflows

• Use cancel-in-progress to suppress multiple jobs for multiple pushes to the same pull request

• Uncheck branch protection rule “Require branches to be up to date before merging” to reduce number of runs
  • Potentially add a scheduled run if you are concerned about incompatible PRs getting merged

Via built-in GitHub YAML syntax:

https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches#require-status-checks-before-merging

Via third-party GitHub Action: https://github.com/dorny/paths-filter

• Use filters to eliminate unnecessary runs
  • Documentation PRs shouldn’t require building and testing code.

• Consider custom docker images for CI with pre-installed and pre-configured dependencies

• Consider running some jobs on schedule (nightly) rather than on each pull request (e.g. full matrix of platform tests, expensive security scans, code coverage)

• Inspect Github Actions run results on your own fork prior to opening Pull Request

• Contact Hyperledger staff for the possibility of dedicated paid runners

• Consider using development container images which come pre-installed with all the dependencies a contributor need to get started with writing code on the project.

• Consider leveraging pre-commit hooks via tools like husky (NodeJS) and lint-staged which can run arbitrary scripts at the time of you making a git commit.

• https://www.npmjs.com/package/lint-staged
• https://www.npmjs.com/package/husky
• https://www.npmjs.com/package/@commitlint/cli