You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CODE_OF_CONDUCT.md
+1-4Lines changed: 1 addition & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,6 @@
3
3
The CoreZipCode code of conduct is derived from the Ruby code of conduct. Any violations of the code of conduct may be reported to Danilo Lutz (danilolutz@gmail.com).
4
4
5
5
- Participants will be tolerant of opposing views.
6
-
7
6
- Participants must ensure that their language and actions are free of personal attacks and disparaging personal remarks.
8
-
9
7
- When interpreting the words and actions of others, participants should always assume good intentions.
10
-
11
-
- Behavior which can be reasonably considered harassment will not be tolerated.
8
+
- Behavior which can be reasonably considered harassment will not be tolerated.
-[KISS - Keep It Simple, Stupid](https://en.wikipedia.org/wiki/KISS_principle)
25
+
-[YAGNI - You Aren't Gonna Need It](https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it)
26
26
27
27
## Reporting an Issue
28
28
@@ -64,16 +64,16 @@ Maybe you ask yourself: _How can I contribute?_ or _What i can do?_
64
64
65
65
We'll help you:
66
66
67
-
* You can implement you favorite zipcode or postcode service and submit to CoreZipCode to be an out-of-the-box service;
68
-
* You can find and fix bugs;
69
-
* Implement openned issues;
70
-
* Improve the CoreZipCode programming.
67
+
- You can implement you favorite zipcode or postcode service and submit to CoreZipCode to be an out-of-the-box service;
68
+
- You can find and fix bugs;
69
+
- Implement openned issues;
70
+
- Improve the CoreZipCode programming.
71
71
72
72
**Only thing will be required by us to approve the pull requests are the unit tests (with correct code coverage) for the new implementations**.
73
73
74
74
## Testing
75
75
76
-
You already know how it's works, just add you test class in ```CoreZipCode.Tests``` project, implement it, run the unit tests, be sure everything is okay and submit to repo.
76
+
You already know how it's works, just add you test class in `CoreZipCode.Tests` project, implement it, run the unit tests, be sure everything is okay and submit to repo.
77
77
78
78
To run the tests go to solution folder and execute:
79
79
@@ -88,6 +88,7 @@ dotnet test CoreZipCode.Tests/CoreZipCode.Tests.csproj -p:CollectCoverage=true -
And open the file `CoreZipCode.Tests/.coverage/index.htm` to see how the unit tests are affecting the code coverage.
92
93
93
94
> **NOTE**: You need to have [ReportGenerator](https://www.nuget.org/packages/dotnet-reportgenerator-globaltool) installed. Use the follow command: `dotnet tool install -g dotnet-reportgenerator-globaltool` to install it globally.
0 commit comments