CAP Issues Tracker

Welcome to the CAP Issues Tracker! This repository is dedicated to reporting, tracking, and managing issues related to the CAP Composer tool. If you encounter any bugs, have feature requests, or need help, please follow the guidelines below to submit your issue.

Table of Contents

1. Introduction
2. How to Report an Issue
   • 1. Search for Existing Issues
   • 2. Create a New Issue
3. Issue Templates
4. Labeling Your Issue
5. Communication and Updates
6. Code of Conduct
7. Contact Us

Introduction

This repository is used for tracking issues related to the CAP Composer tool. Whether you are experiencing a bug, have a suggestion, or require assistance, please create an issue following the steps outlined below.

How to Report an Issue

1. Search for Existing Issues

Before creating a new issue, please check if your issue has already been reported by searching the Issues tab. This helps in reducing duplicates and ensures that all relevant discussions are centralized.

2. Create a New Issue

If your issue is not already listed, you can create a new one by following these steps:

1. Go to the Issues Tab: Navigate to the Issues tab of this repository.
2. Click on "New Issue": Click on the "New Issue" button to create a new issue.
3. Select the Appropriate Issue Template: Choose the most relevant issue template from the list provided. Each template is tailored for different types of issues such as bugs, feature requests, or general questions.
4. Fill Out the Issue Form: Provide a clear and descriptive title for your issue. Fill out the form with all the relevant information, such as:
   • A brief summary of the issue.
   • Steps to reproduce the issue.
   • Expected behavior versus actual behavior.
   • Any relevant screenshots, logs, or code snippets.
   • Environment details (e.g., version of CAP Composer, OS, etc.).
5. Submit the Issue: Once all necessary details are filled in, click the "Submit new issue" button.

Issue Templates

We have provided different issue templates to streamline the process of reporting issues. Please choose the template that best fits your scenario:

• Bug Report: For reporting bugs or unexpected behavior.
• Question: For general inquiries or discussions.
• Other: For issues that don’t fit the above categories.

Labeling Your Issue

After submitting your issue, the maintainers will review it and may apply labels to categorize it. These labels help in prioritizing and managing the issues effectively. Common labels include:

• bug
• question
• help wanted

Communication and Updates

Once your issue is submitted, our team will review it and may ask for additional information. Please monitor your issue and respond promptly if additional details are requested. You will also receive updates as the issue progresses, such as when it is being worked on or when a fix has been deployed.

Code of Conduct

We aim to foster a positive and respectful community. By participating in this repository, you agree to abide by our Code of Conduct.

---

This template should help guide users through the process of reporting issues and ensure they provide all necessary information. You can customize it further to meet your specific needs.