This PR template is the default for all application repositories across Data Engineering, Data Science, DPE, and Content Engineering. It is intended to give engineers across all teams an easy reference to change criteria which must be addressed under relevant circumstances. PRs are intended to be living "sub-repositories" until merged or closed, and it is expected that a PR be created as the first step of the execution development stage (after planning and design).
- Summary: must be completed
- Links: must be completed
- Major Changes: delete if not relevant
- No Major Changes: delete if not relevant
- Major Changes: Required Tasks: complete if any major changes are included in this PR
- Architecture Changes: delete if not relevant
Give a brief summary of the changes included in this PR
This section should include relevant links to documents or issues created during the planning phase which lead to this PR. It is expected that at least one link should exist in this list (because code should only be written in response to some kind of requirement). For example:
- Link to approved product requirements (Confluence)
- Link to Figma designs
- Link to JIRA Epic, or issues filter, or specific issue (bug fix)
- Link to the associated Terraform repository, if architecture changes are included
Delete this section if you do not have major or architecture changes
Select each of the following if it is relevant to this PR:
- New System or Product?
- Change to CDN Rule(s)?
- Abnormal roll-out complexity or risk?
- Abnormal roll-back complexity or risk?
- Is downtime required during deployment?
- New architecture components?
If you selected any of the above options, you must raise an issue in the Changes Repository
Delete this section if you do have major changes.
- No major changes in this PR