-
Notifications
You must be signed in to change notification settings - Fork 0
Description
JIRA Issue: View Issue
Original Description:
No description provided in JIRA issue.
Always make a PR with your changes.
If this is a code (not a config or infrastructure) change: add or edit existing unit tests to cover your changes.
Always look for similar functionality in the codebase before adding new classes. Can this change live in an existing class ?
Avoid deleting fields from proto files unless explicitly told to do it. Opt to mark as deprecated instead.
If your changes touch multiple files, consider breaking them up in multiple commits split by similar functionality. Always bundle code change + changes to the related unit tests in the same commits.
Ultrathink about your instructions, make a detailed plan, and track your progress as you execute it.
@goosebotgh go !