Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Abuse prevention: Ability to block workspaces by repository #9639

Closed
geropl opened this issue Apr 29, 2022 · 2 comments · Fixed by #9762
Closed

Abuse prevention: Ability to block workspaces by repository #9639

geropl opened this issue Apr 29, 2022 · 2 comments · Fixed by #9762
Assignees
Labels
aspect: abuse component: server operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code

Comments

@geropl
Copy link
Member

geropl commented Apr 29, 2022

We saw a lot of (unintentional?) abuse over the last two weeks, mainly induced by this repository.

In general it would be nice to be able to quickly respond to abuse/performance issues by (temporarily) blocking certain repositories.

@geropl geropl added component: server type: improvement Improves an existing feature or existing code team: webapp Issue belongs to the WebApp team aspect: abuse labels Apr 29, 2022
@csweichel csweichel added operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting labels May 4, 2022
@jldec jldec moved this to Scheduled in 🍎 WebApp Team May 4, 2022
@jldec
Copy link
Contributor

jldec commented May 4, 2022

scheduled

@AlexTugarev AlexTugarev self-assigned this May 4, 2022
@AlexTugarev
Copy link
Member

Taking it from here.

@geropl geropl moved this from Scheduled to In Progress in 🍎 WebApp Team May 4, 2022
Repository owner moved this from In Progress to Done in 🍎 WebApp Team May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
aspect: abuse component: server operations: past incident This issue arose during a past incident or its post-mortem priority: highest (user impact) Directly user impacting team: webapp Issue belongs to the WebApp team type: improvement Improves an existing feature or existing code
Projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants