Dapper project contribution guidelines
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Hello,
Recently I started to build a Dapper.UnitOfWork to use in some projects mine that using Dapper and I think, when I finished, maybe I could contribute with dapper community sharing my Dapper.UnitOfWork nuget code.
So, I'd like to know if the Dapper project exists some document with guidelines about some patterns to coding and sharing, for I can do the necessary updates in my code and branch before I create a pull request
Sorry if it's a basic question but it's a first time I'm try to contribute with an open source project
Thank You
Alexandre
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, test, or entry point, and it asks whether contribution guidelines exist rather than identifying a documentation change. First check the repository's existing contribution guidance; the work is complete only when a concrete, agreed documentation scope is defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100