-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
feat(aci): add more action nodes #91607
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
Conversation
9dd40b7
to
a0504d5
Compare
useEffect(() => { | ||
fetchOrgMembers(api, organization.slug); | ||
}, [api, organization]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need this for the SelectMembers component in the email action to properly load
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case, is there any way to move this to the email action component itself? This feels out of place when scanning this file, especially without a comment.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I originally had this in the email action component, but then I realized that this would be called for each instance of the component vs. having this at the top-level within the automation builder, where it would only get called once. We will also need the org members data for one of the data condition nodes (screenshot below). Let me know if you still think it should be within the component!

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think it should be moved down to the component! Ideally this fetch call should be deduplicated by taking advantage of React Query, but that probably needs to be done in a separate PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For now I'd just add an inline comment explaining why this is here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Few things to take another pass at, but overall looks really clean. Nice work! 👍
useEffect(() => { | ||
fetchOrgMembers(api, organization.slug); | ||
}, [api, organization]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case, is there any way to move this to the email action component itself? This feels out of place when scanning this file, especially without a comment.
static/app/views/automations/components/actions/azureDevOps.tsx
Outdated
Show resolved
Hide resolved
adding more action nodes (azure devops, email, github, github enterprise, jira, jira server, opsgenie, pagerduty, slack) preview [here](https://sentry-73eqbmn2e.sentry.dev/issues/automations/new/settings) <img width="1147" alt="Screenshot 2025-05-13 at 5 28 18 PM" src="https://github.com/user-attachments/assets/e9d8c573-b02f-400a-9194-80514c9975d9" /> ### next to-dos: - still need to refactor the ticketing action modal for the ticketing action nodes to be complete (coming in a future PR) - plugin action - webhook action - sentry app actions
adding more action nodes (azure devops, email, github, github enterprise, jira, jira server, opsgenie, pagerduty, slack)
preview here

next to-dos: