Include labels in sample data in issue triggers #78
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
tommoor
approved these changes
Oct 16, 2024
leelasn
deleted the
leela/fea-3640-return-issue-label-data-in-the-createdupdated-issue-zapier
branch
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.
Diff is best viewed without whitespace.
Label data is exposed in issue webhooks, so the new triggers do already expose them. However, the sample data we fetch from the API when a user is creating a new zap doesn't expose them yet, so users don't have a good way to know that they can actually access these fields. This PR begins fetching labels from the API when querying it for sample data.