Skip to content

Commit 6b52f9f

Browse files
committed
Add documentation
Signed-off-by: Owais <owaiskazi19@gmail.com>
1 parent c95f53e commit 6b52f9f

File tree

2 files changed

+20
-1
lines changed

2 files changed

+20
-1
lines changed

CHANGELOG.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Inspired from [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
1919

2020

2121
### Enhancements
22-
- Github workflow for changelog verification ([#1413](https://github.com/opensearch-project/anomaly-detection/pull/1412))
22+
- Github workflow for changelog verification ([#1413](https://github.com/opensearch-project/anomaly-detection/pull/1413))
2323
### Bug Fixes
2424

2525
### Infrastructure

DEVELOPER_GUIDE.md

+19
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@
1111
- [Backports](#backports)
1212
- [Gradle Plugins](#gradle-plugins)
1313
- [Distribution Download Plugin](#distribution-download-plugin)
14+
- [Chaneglog](#changelog)
15+
- [How to add my changes to [CHANGELOG](CHANGELOG.md)?](#how-to-add-my-changes-to-changelog)
1416

1517
## Developer Guide
1618

@@ -102,3 +104,20 @@ The Distribution Download plugin downloads the latest version of OpenSearch by d
102104
```
103105
./gradlew integTest -PcustomDistributionUrl="https://ci.opensearch.org/ci/dbc/bundle-build/1.2.0/1127/linux/x64/dist/opensearch-1.2.0-linux-x64.tar.gz"
104106
```
107+
108+
## Changelog
109+
110+
AD maintains version specific changelog by enforcing a change to the ongoing [CHANGELOG](CHANGELOG.md) file adhering to the [Keep A Changelog](https://keepachangelog.com/en/1.1.0/) format.
111+
112+
Briefly, the changes are curated by version, with the changes to the main branch added chronologically to `Unreleased` version. Further, each version has corresponding sections which list out the category of the change - `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`.
113+
114+
#### How to add my changes to [CHANGELOG](CHANGELOG.md)?
115+
116+
As a contributor, you must ensure that every pull request has the changes listed out within the corresponding version and appropriate section of [CHANGELOG](CHANGELOG.md) file.
117+
118+
Adding in the change is two step process -
119+
1. Add your changes to the corresponding section within the CHANGELOG file with dummy pull request information, publish the PR
120+
121+
`Your change here ([#PR_NUMBER](PR_URL))`
122+
123+
2. Update the entry for your change in [`CHANGELOG.md`](CHANGELOG.md) and make sure that you reference the pull request there.

0 commit comments

Comments
 (0)