---
name: emberbsd-contribute
description: Use when submitting an authorized shared EmberBSD fix, port, example, or documentation change.
---

# Submit a shared change

Read the target's contribution rules, license, and current AI policy.
Read [submission checks](references/submission-checks.md).
For GitHub, read [PR commands](references/github-pr.md).

1. Identify the owner, accepted base, and actual submission channel.
2. Reproduce the problem and prepare a focused fix.
3. Run the required checks on the proposed revision.
4. Inspect the complete diff and preserve source attribution.
5. Push an authorized topic branch or fork branch.
6. Create or update the matching contribution.
7. Report its returned URL and actual state.

Personal application and Ports work does not require publication.
If publication needs separate permission, first prepare a reviewable patch.
Keep private material outside the submission.
Do not overwrite another contributor's branch.
Merge only when authorized.
Use a permitted draft for missing required validation.
Keep failed tests visible.