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: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,7 +99,7 @@ Templates should promote a high contribution quality by referring [contributing
99
99
100
100
### Immutablity
101
101
102
-
GitHub labels should define immutable informations about issues, in order to avoid non-updating scenarios. States should be defined in project section.
102
+
GitHub labels should define immutable informations about issues, in order to avoid non-updated scenarios. States should be defined in project section.
103
103
104
104
**Preferred:**
105
105
```markdown
@@ -115,7 +115,7 @@ GitHub labels should define immutable informations about issues, in order to avo
115
115
116
116
### Colors
117
117
118
-
Colors should be variants of Red-Orange-Green to provide a sense of state. It is better to use similar color styling accross categories for a stronger visual identification. Red being the ones that require the most attention. Green being the ones that require little attention.
118
+
It is better to use similar color styling accross categories for a consistent and stronger visual identification. Colors should be variants of Red-Orange-Green to provide a sense of state. Red being the ones that require the most attention. Green being the ones that require little attention.
119
119
120
120
**Preferred:**
121
121
@@ -133,7 +133,7 @@ Colors should be variants of Red-Orange-Green to provide a sense of state. It is
133
133
134
134
### Categories
135
135
136
-
Labels should help reviewers to quickly get information about the reviewing effort. Labels should be categorized to provide the same amount of information for each issue. Issues cannot have more than one label from the same category.
136
+
Labels should help reviewers to quickly get information about the reviewing effort. Labels should be regrouped into categories to provide consistent information about every issue. Issues cannot have more than one label from the same category.
0 commit comments