Update accounts & settings release docs according to feedback

This commit is contained in:
Pascal Wengerter
2021-04-27 17:18:27 +01:00
parent 95bf02f94f
commit 3957ab96e4
2 changed files with 14 additions and 4 deletions

View File

@@ -8,11 +8,16 @@ geekdocFilePath: releasing.md
{{< toc >}}
## Requirements
You need a working installation of [the Go programming language](https://golang.org/) installed to build the assets for a working release.
## Releasing
After adding changes to the Accounts package within oCIS and testing them locally, you want to update the compiled assets to the oCIS binary.
After adding changes to the accounts package within oCIS and testing them locally, you want to update the compiled assets to the oCIS binary.
To achieve this, you have to run a Go command and add the results to your PR.
To achieve this, you have to run a Go command and add the results to your PR. The preferred way to do this is to run `make generate` in the root
of the repository and then commit the resulting changes to your branch/PR. See below for a way to _only_ build the accounts extension assets.
### Package Hierarchy

View File

@@ -8,11 +8,16 @@ geekdocFilePath: releasing.md
{{< toc >}}
## Requirements
You need a working installation of [the Go programming language](https://golang.org/) installed to build the assets for a working release.
## Releasing
After adding changes to the Settings package within oCIS and testing them locally, you want to update the compiled assets to the oCIS binary.
After adding changes to the settings package within oCIS and testing them locally, you want to update the compiled assets to the oCIS binary.
To achieve this, you have run a Go command and add the results to your PR.
To achieve this, you have to run a Go command and add the results to your PR. The preferred way to do this is to run `make generate` in the root
of the repository and then commit the resulting changes to your branch/PR. See below for a way to _only_ build the settings extension assets.
### Package Hierarchy