Skip to content

Commit 78f5629

Browse files
Improve documentation formatting and clarity in multiple README.md files (#3979)
1 parent 139ed5a commit 78f5629

File tree

10 files changed

+32
-14
lines changed

10 files changed

+32
-14
lines changed

CONTRIBUTING.md

+15-2
Original file line numberDiff line numberDiff line change
@@ -7,13 +7,15 @@ This document explains how to contribute to this project.
77
By contributing you will agree that your contribution will be put under the same license as this repository.
88

99
## Table of Contents
10+
1011
- [Communication](#communication)
1112
- [Quick start](#quick-start)
1213
- [Contributor License Agreement (CLA)](#contributor-license-agreement-cla)
1314
- [Create a fork](#create-a-fork)
1415
- [Quality](#quality)
1516

1617
## Communication
18+
1719
For communication please respect our [FOSS Code of Conduct](https://github.com/mercedes-benz/foss/blob/master/CODE_OF_CONDUCT.md).
1820

1921
IMPORTANT: For contributions or issue reports, please start by creating an [issue on Github](https://github.com/mercedes-benz/sechub/issues).
@@ -23,6 +25,7 @@ Thus, all project-related communication should happen here and in English.<br>
2325
Issue-related communication should happen within the concerned issue.
2426

2527
## Quick Start
28+
2629
Please look at [First steps Wiki page](https://github.com/mercedes-benz/sechub/wiki/First-steps)
2730

2831
## Contributor License Agreement (CLA)
@@ -36,6 +39,7 @@ Before you can contribute, you will need to sign our Contributor License Agreeme
3639
If you are new to contributing in Github, [First Contributions](https://github.com/firstcontributions/first-contributions) might be a good starting point.
3740

3841
## Create a fork
42+
3943
If you would like to contribute code you can do so through Mercedes-Benz GitHub by forking the repository and sending a pull request.
4044

4145
0. Make sure that an [issue on Github](https://github.com/mercedes-benz/sechub/issues) exists for your contribution
@@ -48,42 +52,50 @@ Inside the description it's a good way to mention the related issues with "close
4852
It also will close the linked issue automatically when the pull request is merged!
4953

5054
An example pull request description:
55+
5156
```
5257
This PR
5358
- closes #868
5459
```
5560

5661
### Examples for new contributors
62+
5763
- With [feature issue #633](https://github.com/mercedes-benz/sechub/issues/633) all commits are in a dedicated ordering and contain detailed information about the different steps which were necessary.
58-
- Please look also into the PR description at https://github.com/mercedes-benz/sechub/pull/1029
64+
- Please look also into the PR description at <https://github.com/mercedes-benz/sechub/pull/1029>
5965

6066
## Quality
67+
6168
We assume that for every non-trivial contribution, the project has been built and tested prior to the contribution.
6269

6370
### Documentation
71+
6472
Please ensure that for all contributions, the corresponding documentation is in-sync and up-to-date. All documentation is in English language.
6573

6674
Please see [here](https://mercedes-benz.github.io/sechub/latest/sechub-techdoc.html#section-documentation) for details about documentation.
6775

68-
6976
### Commit messages
77+
7078
GitHub has the possibility to link commits automatically inside issues when mentioned with #${issue number} inside the commit headline.<br>
7179
To make things easier to follow/maintain, please always provide commit message in following style:
7280

7381
```
7482
Dedicated short message what was done #${issue number}
7583
```
84+
7685
or
86+
7787
```
7888
Dedicated short message what was done #${issue number}
7989
8090
- detail1
8191
- detail2
8292
- ...
8393
```
94+
8495
NOTE: Here you MUST add an empty second line between headline and details. It's common practice for GIT.
8596

8697
Example:
98+
8799
```
88100
Described commit message format #868
89101
@@ -92,6 +104,7 @@ Described commit message format #868
92104
```
93105

94106
### Development tools setup
107+
95108
This depends on you which kind of IDE you use for development. But we have some defaults defined - e.g. for git configuration which should be used.
96109

97110
Please check our [development-setup documentation](https://mercedes-benz.github.io/sechub/latest/sechub-techdoc.html#development-setup) for details.

MAINTAINERS.md

-1
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,6 @@
1212
| Laura Bottner | <[email protected]> | [lorriborri](https://github.com/lorriborri) | Mercedes-Benz Tech Innovation GmbH, [imprint](https://github.com/mercedes-benz/foss/blob/master/PROVIDER_INFORMATION.md) | 2023-09-06 |
1313
| Hamid Ahmetovic | <[email protected]> | [hamidonos](https://github.com/hamidonos) | Mercedes-Benz Tech Innovation GmbH, [imprint](https://github.com/mercedes-benz/foss/blob/master/PROVIDER_INFORMATION.md) | 2024-06-06 |
1414

15-
1615
## Emeritus Maintainers
1716

1817
| Maintainer | Email | GitHub ID | Affiliation | Joined | Left |

SECURITY.md

-2
Original file line numberDiff line numberDiff line change
@@ -2,5 +2,3 @@
22
It is Mercedes-Benz’s goal to offer its customers the best and most secure products such as connected cars and other services. Mercedes-Benz values the work of security researchers and whitehat hackers who spend time and effort helping us to achieve this goal.
33

44
For further Information please visit our [Vulnerability disclosure program](https://www.mercedes-benz.com/en/whitehat/).
5-
6-

ide-plugins/eclipse/README.md

+1
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@
22
![Java build (no eclipse parts)](https://github.com/mercedes-benz/sechub-plugin-eclipse/workflows/Java%20build%20(no%20eclipse%20parts)/badge.svg)
33

44
# SecHub Eclipse Plugin
5+
56
![SecHub Logo](https://github.com/mercedes-benz/sechub-plugin-eclipse/blob/master/sechub-eclipse-other/images/sechub-logo-big.png)
67

78
## Intended Usage

ide-plugins/jetbrains/README.md

+8-1
Original file line numberDiff line numberDiff line change
@@ -2,32 +2,39 @@
22
![Java build](https://github.com/mercedes-benz/sechub-plugin-intellij/workflows/Java%20build/badge.svg)
33

44
# SecHub IntelliJ Plugin
5+
56
![SecHub Logo](https://github.com/mercedes-benz/sechub-plugin-intellij/blob/master/other/images/sechub-logo-big.png)
67

78
## Intended Usage
9+
810
This is an IntelliJ plugin for a convenient IDE integration of [SecHub](https://github.com/mercedes-benz/sechub)
911

1012
Please look at [user guide](src/docs/asciidoc/user-guide.adoc) for more information.
1113

12-
1314
## Installation
15+
1416
You will find the plugin at IntelliJ marketplace when searching for term `sechub`
1517
<sup>(it's also listed at https://plugins.jetbrains.com/plugin/23379-sechub).</sup>
1618

1719
### Stable versions
20+
1821
Simply search for term `sechub` in your marketplace settings and install the latest plugin.
1922

2023
## Contributing
24+
2125
We welcome any contributions.
2226
If you want to contribute to this project, please read the [contributing guide](CONTRIBUTING.md).
2327

2428
## Code of Conduct
29+
2530
Please read our [Code of Conduct](https://github.com/mercedes-benz/foss/blob/master/CODE_OF_CONDUCT.md) as it is our base for interaction.
2631

2732
## License
33+
2834
This project is licensed under the [MIT LICENSE](LICENSE).
2935

3036
## Provider Information
37+
3138
Please visit <https://www.mercedes-benz-techinnovation.com/en/imprint/> for information on the provider.
3239

3340
Notice: Before you use the program in productive use, please take all necessary precautions,

ide-plugins/vscode/README.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ Recommended: Install the plugin from the Open-VSX marketplace from within [VSCod
1515

1616
For VS Code you need to download the [plugin](https://open-vsx.org/extension/mercedes-benz/sechub) and install it manually. It is also possible to install the plugin manually in VSCodium and Eclipse Theia.
1717

18-
NOTE: Please use the new plugin from Mercedes-Benz: https://open-vsx.org/extension/mercedes-benz/sechub. The old Daimler plugin will be deprecated. The reason for the deprecation is the rebranding of Daimler to Mercedes-Benz.
18+
NOTE: Please use the new plugin from Mercedes-Benz: <https://open-vsx.org/extension/mercedes-benz/sechub>. The old Daimler plugin will be deprecated. The reason for the deprecation is the rebranding of Daimler to Mercedes-Benz.
1919

2020
## Development
2121

@@ -104,4 +104,3 @@ Please visit https://www.mercedes-benz-techinnovation.com/en/imprint/ for inform
104104
Notice: Before you use the program in productive use, please take all necessary precautions,
105105
e.g. testing and verifying the program with regard to your specific use.
106106
The program was tested solely for our own use cases, which might differ from yours.
107-

sechub-cli/src/mercedes-benz.com/sechub/cli/testdata/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -2,4 +2,4 @@
22
# README.md
33

44
This folder is called `testdata` so go will ignore this at build time!
5-
(this behaviour is used by standard library as well, see https://golang.org/src/cmd/gofmt/testdata/)
5+
(this behaviour is used by standard library as well, see <https://golang.org/src/cmd/gofmt/testdata/>)
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,19 @@
11
<!-- SPDX-License-Identifier: MIT --->
22
# About this folder
3+
34
It will be used for exclude mechanism working on sechub client uploading.
45
`sechub-integrationtest-client-sourcescan-exluded_some_files.json`
56
does simple exclude this `README.md` and all `exclude-me.txt` files
67

78
## Where is this file used?
9+
810
See `SecHubExecutionScenarioSecHubClientIntTest.java` and also `sechub-integrationtest-client-sourcescan-excluded_some_files.json`
911

1012
## Warning
13+
1114
Please do not change the content of this folder and subfolders because the exclude
1215
check is done by creating a checksum which is calculated without the excluded files.
1316
So changing content of included parts will fail test! If you must change the files be aware
1417
to create a windows and a Linux checksum. Why? Because zip files generated for windows are always
1518
a little different than on Linux - even when same content. Maybe paths or a hidden OS stamp...
16-
In order to prevent build and test problems we provide 2 dedicated sha256 keys: one for Windows another for Linux.
19+
In order to prevent build and test problems we provide 2 dedicated sha256 keys: one for Windows another for Linux.

sechub-pds/src/main/resources/certificates-untracked/README.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ About p12 folder
44
========================
55

66
Here your p12 certificates have to be stored
7+
78
- local development
89
- prod
910
- ..
@@ -12,5 +13,3 @@ Inside this folder GIT does ignore anything except this `README.md`!
1213

1314
Why?
1415
----
15-
16-

sechub-server/src/main/resources/certificates-untracked/README.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ About p12 folder
44
========================
55

66
Here your p12 certificates have to be stored
7+
78
- local development
89
- prod
910
- ..
@@ -12,5 +13,3 @@ Inside this folder GIT does ignore anything except this `README.md`!
1213

1314
Why?
1415
----
15-
16-

0 commit comments

Comments
 (0)