Skip to content
This repository was archived by the owner on Mar 14, 2024. It is now read-only.

Latest commit

 

History

History
69 lines (43 loc) · 2.91 KB

CONTRIBUTING_DCO.md

File metadata and controls

69 lines (43 loc) · 2.91 KB

Contributing to api-data-collector

API Data Collector (ADC) team welcome contributions from the community and first want to thank you for taking the time to contribute!

Please familiarize yourself with the Code of Conduct before contributing.

Before you start working with api-data-collector, please read our Developer Certificate of Origin. All contributions to this repository must be signed as described on that page. Your signature certifies that you wrote the patch or have the right to pass it on as an open-source patch.

Ways to contribute

We welcome many different types of contributions and not all of them need a Pull request. Contributions may include:

  • New features and proposals
  • Documentation
  • Bug fixes
  • Issue Triage
  • Answering questions and giving feedback
  • Helping to onboard new contributors
  • Other related activities

Getting started

Because ADC is a Chrome DevTools extension, you need to know how to use or test it:

  • Chrome DevTools: go to chrome://extensions/, then choose either Upload unpacked or Update for local testing this ADC extension
  • Open Chrome DevTools, then find and click on the ADC tab to use it

Contribution Flow

This is a rough outline of what a contributor's workflow looks like:

Create a topic branch in your fork from where you want to base your work Make commits of logical units Make sure your commit messages are with the proper format, quality and descriptiveness (see below) Push your changes to the topic branch in your fork Create a pull request containing that commit

We follow the GitHub workflow and you can find more details on the GitHub flow documentation.

Example: git remote add upstream https://github.com/vmware-labs/api-data-collector.git git checkout -b my-new-feature main git commit -a git push origin my-new-feature

Pull Request Checklist

Before submitting your pull request, we advise you to use the following:

  1. Check if your code changes will pass both code linting checks and unit tests.
  2. Ensure your commit messages are descriptive. We follow the conventions on How to Write a Git Commit Message. Be sure to include any related GitHub issue references in the commit message. See GFM syntax for referencing issues and commits.
  3. Check the commits and commits messages and ensure they are free from typos.

Reporting Bugs and Creating Issues

For specifics on what to include in your report, please follow the guidelines in the issue and pull request templates when available.

Ask for Help

The best way to reach us with a question when contributing is to ask on:

  • The original GitHub issue
  • The developer mailing list
  • Our Slack channel

Additional Resources