Skip to content

Use .rubocop.yml

Trevor Vallender requested to merge fix-rubocop into master

Notes from the developer

How to start testing

[Are there any specific settings, external APIs, or knowledge needed for testing?]

Things to watch out for / Gotchas

[What is most likely to trip up or confuse a tester?]

Links to the relevant documentation

[What new docs have you created? What existing (external?) docs have you used?]

Development concerns

(If you don't/can't tick any of the items below, please include an explication)

Pre-development

  • If necessary, I have created/updated an ADR which explains the changes I intend to make
  • I have conducted a 0% code review with another member of the team

Post-development

  • If there is one, I have reviewed and amended the ADR
  • If necessary, I have made appropriate changes to the development seed data related to this change
  • I have added or updated any relevant documentation (readme, documentation library, etc..)
  • I have added new tests where relevant
  • I have updated the CHANGELOG accordingly
  • If a gem version has been locked, I've documented why

QA/QC concerns

Testing

  • I have read any documentation (including commit messages) and approve their contents
  • I have verified the acceptance criteria are met
  • I have reviewed the code with the Foxsoft Development Guidelines in mind

Pull request template V1.9 (https://git.foxsoft.co.uk/foxsoft/project-templates/-/blob/main/.gitlab/merge_request_templates/feature.md)

Merge request reports

Loading