Safety Culture Pull Request checklist | Process Street Safety Culture Pull Request checklist – Process Street

Is the code understandable?

Does the code fit the purpose it was intended for?

Have any configuration additions or changes been added to the configuration service already?

Are dependencies on other changes clearly specified (or preferably avoided)

Has it had a secondary review from someone familiar with the service or technology if needed?

If package.json was changed, has shrink wrap been rerun?

Does the code contain adequate logging for troubleshooting production issues?

Are any new features hidden behind a feature flag or other restriction?

Will production features continue working if feature flags are disabled?

Does it have adequate unit tests for new code, or add testing for existing code?

Is the code able to be deployed into production now?