See: https://github.com/civicrm/civicrm-core/pull/14184

Need SUPER privilege for database user

Added triage guidelines to the docs

Update hook_civicrm_contact_get_displayname.md

Fix typo

update the example to use a valid $asset name

Spelling: rational vs rationale

Docs make it clear that clear is the preferred method

Add in documentation of crmType and phpType setting now avaliable as …

Add event-billing-block descriptions

Add CaseContact to hook_civicrm_post() and hook_civicrm_pre() documen…

Add CaseContact to hook_civicrm_post() and hook_civicrm_pre() documentation - see https://github.com/civicrm/civicrm-core/pull/14030

Reposition 'Campaign' in list to be alphabetical

update pr-review guide to solve issue #598

show new way for accessing pr test site credentials

Add link to information about localising fields

Remove the most painfully out of date parts of this page

Much more could be done but this is probably worth doing as a light edit

Changing flush to clear as the preferred method. I think when it was added there was an assumption devs would be developing against < 5.4 so it made sense to give primacy to flush but times have changed

@totten

Correct function name

Documented pseudofield property of filters.

Corrected errors in and reorganized hook_civicrm_apiWrappers() documentation

don't include deprecated attribute in example

clarify meaning of is_contact and is_domain

Update hook_civicrm_aclWhereClause.md

Remove 4.4 references - too old now

Update hook_civicrm_aclWhereClause.md

removed reference to the LTS

Ripped out some old stuff

Update bootstrap.md

Add hook_civicrm_findDuplicates documentation

Add explanation about interactive rebasing

I didn't add in the ESR as I don't believe the policy  is clear enough to be documented but generally I understand that the discussion takes place on the ESR channel & PRs are not really encouraged against the branch - the CT would do a PR if they decide to backport or agree someone else would