PULL_REQUEST_TEMPLATE.md

Is this a PR to the develop branch of cf-deployment?

Only PR's to develop are accepted.

WHAT is this change about?

Describe the change.

WHY is this change being made (What problem is being addressed)?

Understanding why this change is being made is fantastically helpful. Please do tell...

Please provide contextual information.

Include any links to other PRs, stories, slack discussions, etc... that will help establish context.

Has a cf-deployment including this change passed our cf-acceptance-tests?

• YES
• NO

How should this change be described in cf-deployment release notes?

Something brief that conveys the change and is written with the Operator audience in mind. See previous release notes for examples.

Does this PR introduce a breaking change?

Does this introduce changes that would require operators to take action in order to deploy without a failure? Please see below for few examples.

If you're promoting an experimental Ops-file (or removing one), Please follow the Ops-file workflows.

Examples of breaking changes:

• changes the name of a job or instance group
• moves a job to a different instance group
• deletes a job or instance group
• changes the name of a credential
• requires out-of-band manual intervention on the part of the operator
• removes Ops-file (e.g. from ./operations/ or ./operations/experimental folders)

Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?

• YES - please specify
• NO

Will this change increase the VM footprint of cf-deployment?

• YES - does it really have to?
• NO

Does this PR make a change to an experimental or GA'd feature/component?

• experimental feature/component
• GA'd feature/component

What is the level of urgency for publishing this change?

• Urgent - unblocks current or future work
• Slightly Less than Urgent

Tag your pair, your PM, and/or team!

It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.