Skip to content

A local-first personal finance app

Update README.md (#183)

Rich Howell3817952ed64e
diff --git a/README.md b/README.md
index 69c3e89950..8c058ac70e 100644
--- a/README.md
+++ b/README.md
@@ -213,24 +213,4 @@ If you are using GitHub pages for hosting, this command is a convenient way to b
### Writing Good Release Notes
-Create a Markdown file in the `upcoming-release-notes` directory of the repository you’re contributing to named after the PR number. The file should contain front matter with a `category` key (defining which header to put the entry under) and an `authors` key (defining the author of the entry). The body of the file should contain the changelog entry. Keep it short and clear — ideally one sentence, and also non-technical (unless the category is “Maintenance”). Copy-paste the template below to get started!
-
-```markdown
----
-category: Features
-authors: [YourGitHubUsername]
----
-
-Add option to include exchange rate multiplier during import
-```
-
-Valid categories:
-
-- `Features`: New features
-- `Enhancements`: Improvements to existing features
-- `Bugfix`: Bug fixes
-- `Maintenance`: Internal changes that don’t directly affect users
-
-The `authors` key should be an array with the GitHub usernames of the people who contributed to the PR. In most cases, this should just be you but you can add multiple people if needed.
-
-Try to phrase your message as a command, e.g. “Add option to include exchange rate multiplier during import” rather than “Added option to include exchange rate multiplier during import” or “Adds option to include exchange rate multiplier during import.” Generally your message should match the PR title, but you can change it if you think it’s more clear.
+This is detailed in the [contributing](https://actualbudget.org/docs/contributing/) section of the documentation.