Commit 562eace
committed
Deprecate use of organisation api keys
With private repos we can use user's permissions on a repo to easily determine whether they should have read access to the repo. This relationship is a lot more muddy with organisations.
Organisations can own lots of repos but who should have access to those API keys? It's all a bit complicated and frankly not worth the effort. So, it's easier to deprecate organisation API keys.
There are only a very small handful of organisation API keys in use at the moment. So, it's not a big problem really.1 parent 16ae8a5 commit 562eace
1 file changed
Lines changed: 0 additions & 14 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
84 | 84 | | |
85 | 85 | | |
86 | 86 | | |
87 | | - | |
88 | | - | |
89 | | - | |
90 | | - | |
91 | 87 | | |
92 | 88 | | |
93 | 89 | | |
| |||
143 | 139 | | |
144 | 140 | | |
145 | 141 | | |
146 | | - | |
147 | | - | |
148 | | - | |
149 | | - | |
150 | | - | |
151 | | - | |
152 | | - | |
153 | | - | |
154 | 142 | | |
155 | 143 | | |
156 | 144 | | |
| |||
206 | 194 | | |
207 | 195 | | |
208 | 196 | | |
209 | | - | |
210 | 197 | | |
211 | 198 | | |
212 | 199 | | |
213 | 200 | | |
214 | 201 | | |
215 | | - | |
216 | 202 | | |
217 | 203 | | |
218 | 204 | | |
| |||
0 commit comments