Files
Palmr/apps/docs/content/docs/1.1.7-beta/open-an-issue.md
Daniel Luiz Alves c1fc52c302 feat(docs): migrate documentation to Next.js with Fumadocs
This commit migrates the documentation site from Astro to Next.js, leveraging Fumadocs for enhanced functionality and maintainability. The migration includes:
- New Next.js configuration and setup
- Integration of Fumadocs for documentation rendering
- Addition of new documentation assets and images
- Removal of Astro-related files and configurations

The migration aims to improve the documentation site's performance, scalability, and developer experience.
2025-04-17 01:15:19 -03:00

3.3 KiB
Raw Blame History

title
title
How to open an issue

Opening an issue on GitHub is a great way to report bugs, request features, or ask questions about a project. This tutorial will guide you through the process of opening an issue for the Palmr. project on GitHub.


Step 1: Log in to GitHub

Before you can star a project, you need to be logged into your GitHub account. If you don't have an account yet, you can sign up for free at GitHub.


Step 2: Go to the Palmr. Repository

Once you're logged in, go to the Palmr. repository by clicking on this link: https://github.com/kyantech/Palmr.

Alternatively, you can search for "Palmr" in the GitHub search bar and click on the repository owned by Kyantech.


Step 3: Navigate to the Issues Tab

On the Palmr repository page, click on the Issues tab near the top of the page. This will take you to the issues section of the repository.

Palmr Profile Menu


Step 4: Click on "New Issue"

Once you're in the issues section, click the New Issue button to start creating a new issue.

Palmr Profile Menu


Step 5: Fill Out the Issue Form

Youll now see a form where you can provide details about your issue. Heres how to fill it out:

  1. Title: Write a clear and concise title that summarizes the issue.
  2. Description: Provide a detailed description of the issue. Include steps to reproduce the problem (if its a bug), expected behavior, and actual behavior. If youre requesting a feature, explain why it would be useful.
  3. Labels (Optional): Add labels to categorize your issue (e.g., bug, enhancement, question). This helps the maintainers organize and prioritize issues.
  4. Attachments (Optional): You can attach screenshots, logs, or other files to help explain the issue.

Palmr Profile Menu


Step 6: Submit the Issue

Once youve filled out the form, click the Create button. Your issue will now be visible to the project maintainers and other contributors.


Tips for Writing a Good Issue

To ensure your issue is addressed quickly and effectively, follow these tips:

  • Be Clear and Specific: Provide as much detail as possible.
  • Use a Descriptive Title: A good title helps maintainers understand the issue at a glance.
  • Include Steps to Reproduce: If its a bug, explain how to reproduce it.
  • Be Polite and Respectful: Remember that maintainers and contributors are volunteering their time.

Why Opening Issues is Important

Opening issues is a key part of contributing to open-source projects. Heres why it matters:

  1. Improves the Project: Your feedback helps identify bugs and suggest new features.
  2. Helps Maintainers: Clear and detailed issues make it easier for maintainers to address problems.
  3. Encourages Collaboration: Issues can spark discussions and attract contributors to help solve problems.

Conclusion

That's it! You've successfully opened an issue for the Palmr project on GitHub. Your contribution helps improve the project and supports the open-source community. Thank you for taking the time to share your feedback!