chore: Add revanced-bot to the exclusion list #233
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Usually this kind of implementation is problematic. What if the API is changed? If different users commit then this filter has no effect. #137 fixes the issue by proposing to add a frontend configuration to the API which would allow configuring the site to match the API. For now this is fine |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not sure what to label this commit, It's not really considered a "feature" or a bug "fix". I'll use chore as miscellaneous.
@revanced-bot has been engaged in ReVanced Manager repository due to Translation CI but not to the point where it should appear in the contributor list as it only recent (4 days ago as of writing), so it would make sense to add @revanced-bot to the exclusion list like semantic-release-bot is.