daniellemaywood.uk
+2
-4
CONTRIBUTING.md
+2
-4
CONTRIBUTING.md
···
35
35
introduces new functionality or behaviour this would be a good time to
36
36
discuss the details of the change to ensure we are in agreement as to how
37
37
the new functionality should work.
38
-
2. Open a GitHub pull request with your changes and ensure the tests and build
38
+
2. Update the [CHANGELOG.md](CHANGELOG.md) file with your changes.
39
+
3. Open a GitHub pull request with your changes and ensure the tests and build
39
40
pass on CI.
40
-
3. Reflect your changes in [CHANGELOG.md](CHANGELOG.md) under Unreleased at the top of the file.
41
-
Find the best section to describe your changes. You can draw inspiration from
42
-
the changes made previously.
43
41
4. A Gleam team member will review the changes and may provide feedback to
44
42
work on. Depending on the change there may be multiple rounds of feedback.
45
43
5. Once the changes have been approved the code will be rebased into the