Skip to content

Conversation

@dustinlessard-wf
Copy link
Contributor

@dustinlessard-wf dustinlessard-wf commented Oct 25, 2023

Motivation

When engineers see a CI check failure, they are not provided any indication of next steps.

1 change(s) needed.

Changes

  • modified failure message to include instructions on how to run the INTLcodemod locally

Screenshot 2023-10-26 at 10 07 04 AM

Release Notes

modify failure message to include instructions on how to run the INTL codemod locally

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

  • Tests were updated and provide good coverage of the changeset and other affected code
  • Manual testing was performed if needed

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

  • A Frontend Frameworks Design member has reviewed these changes
  • There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
  • For release PRs - Version metadata in Rosie comment is correct

@aviary-wf
Copy link

Security Insights

No security relevant content was detected by automated scans.

Action Items

  • Review PR for security impact; comment "security review required" if needed or unsure
  • Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

alanknight-wk
alanknight-wk previously approved these changes Oct 26, 2023
@alanknight-wk
Copy link
Contributor

@Workiva/release-management-p

@dustinlessard-wf
Copy link
Contributor Author

QA+1

Copy link

@rmconsole-wf rmconsole-wf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 from RM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants