Skip to content

Commit 5f59c54

Browse files
authored
Create CONTRIBUTING.md
1 parent a9b4e04 commit 5f59c54

File tree

1 file changed

+49
-0
lines changed

1 file changed

+49
-0
lines changed

CONTRIBUTING.md

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
# ✨ Contributing to WinUI.TableView
2+
3+
Thank you for your interest in contributing to **WinUI.TableView**! We welcome all contributions and appreciate your help in making this project better for everyone.
4+
5+
---
6+
7+
## ❔ Questions
8+
9+
Please search existing [Discussions](../../discussions) first to see if your question has already been answered. If not, feel free to start a new discussion for general questions. Keep GitHub issues focused on actionable bug reports and enhancements.
10+
11+
---
12+
13+
## 🐛 Reporting Bugs
14+
15+
Before reporting a bug, please search existing [Issues](../../issues) to see if it has already been reported. If you find a similar issue, add any additional details as a comment. If not, please [open a new issue](../../issues/new?template=bug_report.md) and provide as much detail as possible to help us reproduce and fix the problem.
16+
17+
---
18+
19+
## 💡 Suggesting Features
20+
21+
Please search existing [Issues](../../issues) and [Discussions](../../discussions) to see if your feature has already been suggested. If you find a similar request, consider adding your thoughts to the existing conversation. If not, please [open a feature request](../../issues/new?template=feature_request.md) and describe your idea.
22+
23+
---
24+
25+
## 🚀 Pull Requests
26+
27+
Before creating a Pull Request, please start a Discussion or open an Issue to describe your planned changes. This helps the maintainers and community provide feedback early and ensures your contribution aligns with the project goals. You can skip this step for minor fixes like typos or small documentation updates.
28+
29+
- Do NOT open pull requests from your `main` branch. Always create a new feature ( for example `add-cell-tests` ) in your fork before submitting a PR.
30+
- Ensure your changes are tested with both WinUI 3 and Uno Platform targets.
31+
- Add or update unit tests and integration tests to cover your changes.
32+
- Complete the PR checklist, and ensure your code is tested with both targets.
33+
- Update documentation as needed to reflect your changes.
34+
35+
[How to create a pull request from a fork (GitHub Docs)](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)
36+
37+
---
38+
39+
## 📝 Code Style
40+
41+
- Follow the existing coding conventions and structure.
42+
- Write clear, concise commit messages.
43+
- Include comments where necessary.
44+
45+
---
46+
47+
## 💙 Thank You
48+
49+
Thank you for being a part of the WinUI.TableView community. Every contribution counts!

0 commit comments

Comments
 (0)