Repository navigation
chore(ci): relay development activity to the family Discord channel - #32
Merged
Merged
Conversation
Contributor
|
Thanks for opening your first pull request on tornadoapi-guard! Quick checklist before review (most of these are enforced by CI, but worth a glance):
See CONTRIBUTING.md for the full workflow and the Code of Conduct for the community standards we follow. Welcome aboard — a maintainer will review shortly. |
This file contains hidden or 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
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.
Delivers issue: none (chore,
no-issue)Forwards issues, pull requests, reviews and discussions from this repository to its language family's development channel on the Guard Core Discord (
#dev-python,#dev-typescript,#dev-rust,#dev-go,#dev-php,#dev-saas).pull_request_targetruns no untrusted code.permissions: {}.DISCORD_DEV_FEED_WEBHOOKrepository secret. Runs without it (fork pull requests) skip with a notice.Release posts stay on the existing GitHub hook to
#releases.