From 25113a915c20dd316facd6928991724608e99350 Mon Sep 17 00:00:00 2001
From: milcastob <43559371+milcastob@users.noreply.github.com>
Date: Fri, 26 Dec 2025 13:57:51 +0100
Subject: [PATCH] docs: add contribution guidelines for Base node

Introduces a clear CONTRIBUTING.md explaining local setup, style, testing, and PR expectations for new contributors.
---
 docs/CONTRIBUTING.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 docs/CONTRIBUTING.md

diff --git a/docs/CONTRIBUTING.md b/docs/CONTRIBUTING.md
new file mode 100644
index 00000000..3a0b62bd
--- /dev/null
+++ b/docs/CONTRIBUTING.md
@@ -0,0 +1,31 @@
+# Contributing to the Base node repository
+
+Thank you for considering a contribution!
+
+## Getting started
+
+1. Fork the repository and clone your fork.
+2. Run `docker compose up` to start a node locally.
+3. Use a new branch per change (`git checkout -b feature/your-description`).
+
+## Code style
+
+- Shell scripts should use `#!/usr/bin/env bash` and `set -euo pipefail`.
+- Go code follows `gofmt` style; run `go fmt ./...` before committing.
+- Document any new files or APIs.
+
+## Testing your changes
+
+- If you modify the compose setup, run `docker compose config` to ensure the YAML is valid.
+- For Go changes, run `go test ./...`.
+- For docs, ensure Markdown renders properly and links are correct.
+
+## Opening a pull request
+
+Describe:
+
+- The purpose of your change.
+- How you tested it.
+- Any related issues it addresses.
+
+Maintainers will review and provide feedback. Welcome aboard!