Skip to content

Commit 5b190d7

Browse files
committed
fix: move stale to state: invalid
1 parent b09bf0d commit 5b190d7

File tree

2 files changed

+2
-5
lines changed

2 files changed

+2
-5
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ There are many very good examples of GitHub Label strategies. Almost all of them
3535
- `state` = describe decision; `approved`, `blocked`, `inactive` or `pending`
3636
- `type` = describe type; `bug`, `chore`, `discussion`, `docs`, `feature`, `fix`, `security`, `testing`
3737
- `work` = describe situation; `chaotic`, `complex`, `complicated` or `obvious`
38-
- The only labels without prefixes are; `breaking`, `good first issue`, `greenkeeper`, `help`, `stale` and `semantic-release`
38+
- The only labels without prefixes are; `breaking`, `good first issue`, `greenkeeper`, `help` and `semantic-release`
3939

4040
The _GitHub Label presets_ are meant to be used with [github-label-sync](https://github.com/Financial-Times/github-label-sync):
4141

labels.json

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,10 +88,6 @@
8888
"Priority: High"
8989
]
9090
},
91-
{
92-
"name": "stale",
93-
"color": "e6e6e6"
94-
},
9591
{
9692
"name": "semantic-release",
9793
"color": "e6e6e6"
@@ -134,6 +130,7 @@
134130
"aliases": [
135131
"duplicate",
136132
"invalid",
133+
"stale",
137134
"Status: Abandoned",
138135
"status: duplicate",
139136
"status: wontfix",

0 commit comments

Comments
 (0)