Skip to content

Latest commit

 

History

History
45 lines (27 loc) · 2 KB

CONTRIBUTING.md

File metadata and controls

45 lines (27 loc) · 2 KB

Contributing Guidelines

The Azure Service Operator project accepts contributions via GitHub pull requests. This document outlines the process to help get your contribution accepted.

Contributor License Agreements

We'd love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.

The Microsoft CLA must be signed by all contributors. Please fill out either the individual or corporate Contributor License Agreement (CLA). Once you are CLA'ed, we'll be able to accept your pull requests.

NOTE: Only original source code from you and other people that have signed the CLA can be accepted into the repository.

How to Contribute a Patch

  1. If you haven't already done so, sign a Contributor License Agreement (see details above).
  2. Fork the desired repo, develop and test your code changes.
  3. Submit a pull request.

Pull Request Titles and Commit Messages

Use Conventional Commits for pull request titles and commit messages: <type>: <short description>.

The prefixes used in this repository are:

  • feat: New features, resources, or API versions.
  • fix: Bug fixes.
  • docs: Documentation changes.
  • test: Test-only changes.
  • perf: Performance improvements.
  • chore: Maintenance, dependency updates, and tooling changes.

For example, use docs: update docs for 2.22 for a release documentation PR.

Contributing to Azure Service Operator v2

See Contributing to Azure Service Operator v2 for instructions on how to build ASO v2 and test your code.

Reporting Security Issues

Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, including this one.

Please do not report security vulnerabilities through public GitHub issues.

Please see reporting security issues for more details on how to report a security issue.