From d8f4d7afe4ed3bc0a584b5c664a5c3ecd8ae43ea Mon Sep 17 00:00:00 2001 From: Dzmitry Tolpekin Date: Fri, 26 Apr 2024 11:30:12 -0400 Subject: [PATCH] Update README.md --- README.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ad43a6634..f186e4849 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,10 @@ [^1]: The demo page source is stored in a directory named `docs` because this is the only non-root directory name that gh-pages can deploy from without creating a custom Github Actions workflow. -## How to investigate a feature +## Filling the data + +### How to investigate a feature + - If there's a test for this feature, that's already enough evidence that it's supported. Mark the feature as "supported" and mention the path to the test source. You're done! - If there's no test for this feature, write one in one of the Surfly suites: @@ -31,6 +34,17 @@ - mark the feature as TODO (or NEVER, or partial, etc.) - create an issue to add support and tests for this feature (and mention your manual testing strategy!) +### Grouping the changes + +Each individual change from CMS results in a commit. Editing support for many features results in commit spam. + +For multiple changes it's recommended to create a separate branch. It can be selected in the top left dropdown in the CMS. + +Once the changes are ready - the PR based on the branch can be squashed and merged. All changes will be grouped in one commit. + + + + ## Known issues - the search feature in the public instance of Pages CMS is not currently working