Skip to content

Add contribution guidance (CONTRIBUTING.md) - #569

Open
dgarske wants to merge 1 commit into
wolfSSL:masterfrom
dgarske:contributing_md
Open

Add contribution guidance (CONTRIBUTING.md)#569
dgarske wants to merge 1 commit into
wolfSSL:masterfrom
dgarske:contributing_md

Conversation

@dgarske

@dgarske dgarske commented Aug 11, 2026

Copy link
Copy Markdown
Member

Description

Adds a CONTRIBUTING.md to the repository root. None of the wolfSSL repositories had one, so our contributor agreement requirement was only discovered after someone had already done the work. See wolfSSL/wolfssh#1146, where an outside contributor withdrew a PR over it and asked us to document the requirement up front.

The same repo-agnostic file is being added to wolfSSL, wolfSSH, wolfMQTT, wolfTPM, wolfBoot, wolfPKCS11, wolfHSM, wolfProvider, wolfSentry and wolfCLU. It covers how to contribute, the contributor agreement and how to request one, our CI (GitHub Actions is public, Jenkins failures get pasted in by a maintainer), coding expectations, and where to report security issues. Please read the file itself rather than a summary here.

Testing

Documentation only - no code changes.

Copilot AI lite review requested due to automatic review settings August 11, 2026 23:00

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds repository-level contribution guidance to wolfMQTT by introducing a new root CONTRIBUTING.md, aiming to document the contributor agreement requirement and general contribution workflow up front.

Changes:

  • Add a new CONTRIBUTING.md covering contribution paths, contributor agreement process, and CI expectations.
  • Document coding expectations (style, C90 constraints, return-code discipline) and security reporting guidance.
Suppressed comments (1)

CONTRIBUTING.md:49

  • These PR submission steps hard-code master as the base branch. Since CI is set up for both master and main in this repo (e.g., .github/workflows/websocket-test.yml:5-8), it’s safer to refer to the repository’s default branch so the guidance remains accurate if the default is main.
1. Fork the repository and create a topic branch off `master`.
2. Keep commits focused; one logical change per commit, with a clear message.
3. Open the pull request against `master`.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread CONTRIBUTING.md
@@ -0,0 +1,97 @@
# Contributing

Thank you for your interest in contributing to wolfSSL. This guide applies to all wolfSSL Inc. repositories (wolfSSL, wolfSSH, wolfTPM, wolfBoot, wolfMQTT, wolfCLU, wolfPKCS11, wolfHSM, wolfProvider, wolfSentry, and the rest). Please read the "Contributor Agreement" section below - it is the one requirement that surprises people, and we would rather you know about it up front.
Comment thread CONTRIBUTING.md

## Before You Start

- **Check `master` first.** The fix may already be in, or the surrounding code may have moved. Please base your work on the current `master`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants