Skip to content

Conversation

aminvakil
Copy link
Collaborator

There is no need to lock issues/PRs on forked repositories, also it faces this error lots of times:
You have exceeded a secondary rate limit. Please wait a few minutes before you try again.

Full list: https://github.com/aminvakil/self-hosted/actions/workflows/lock.yml

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

@BYK BYK requested a review from chadwhitacre February 15, 2023 10:34
@aminvakil
Copy link
Collaborator Author

Something similar has already been done in #1529 .

Other workflows should be investigated as well, so all can be done once.

@hubertdeng123
Copy link
Member

I guess this could also be done for stale.yml if that becomes a problem. Thanks @aminvakil

@hubertdeng123 hubertdeng123 merged commit edcdfd4 into getsentry:master Feb 15, 2023
@aminvakil aminvakil deleted the lock_only_getsentry branch February 15, 2023 23:48
@github-actions github-actions bot locked and limited conversation to collaborators Mar 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants