STARK-1 Update README.md

[pallavielango-git]

Related issue(s)

• [BUGSNAG ISSUE]
• [TICKET_NUMBER]

Description

Post-deployment steps

Type of Change

• Request (code for a specific purpose that will not add a feature. e.g. one off rake task)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Maintenance task (rake tasks or changes that do not change logic tha will affect the application behaviour)

How to test / reproduce

Assignee

The author of the PR (the person who wrote the code) must be one assignee

The person who has tested this in staging, is the second assignee.
This person assigns themselves, when they are going to test this on staging, as part of the review phase of a ticket's lifecycle.

Screenshots

Checklist

• The implementation has been tested locally
• The author of this PR is the Assignee
• The implementation has been tested in staging (and the person (who is not the author) doing it is an assignee of this PR)
  • This cannot be tested on staging, and the reasons why are in the How to test / reproduce section
• There are no typos, spelling, or grammatical errors in end-user facing text
• The Pull Request is tagged with the staging label if it is deployed to staging
• Tests are added where appropriate
• The client/support team have been notified before release, if this change runs migrations or other risky code