You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For communication please respect our [FOSS Code of Conduct](https://github.com/mercedes-benz/foss/blob/master/CODE_OF_CONDUCT.md).
18
20
19
21
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>
23
25
Issue-related communication should happen within the concerned issue.
24
26
25
27
## Quick Start
28
+
26
29
Please look at [First steps Wiki page](https://github.com/mercedes-benz/sechub/wiki/First-steps)
27
30
28
31
## Contributor License Agreement (CLA)
@@ -36,6 +39,7 @@ Before you can contribute, you will need to sign our Contributor License Agreeme
36
39
If you are new to contributing in Github, [First Contributions](https://github.com/firstcontributions/first-contributions) might be a good starting point.
37
40
38
41
## Create a fork
42
+
39
43
If you would like to contribute code you can do so through Mercedes-Benz GitHub by forking the repository and sending a pull request.
40
44
41
45
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
48
52
It also will close the linked issue automatically when the pull request is merged!
49
53
50
54
An example pull request description:
55
+
51
56
```
52
57
This PR
53
58
- closes #868
54
59
```
55
60
56
61
### Examples for new contributors
62
+
57
63
- 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>
59
65
60
66
## Quality
67
+
61
68
We assume that for every non-trivial contribution, the project has been built and tested prior to the contribution.
62
69
63
70
### Documentation
71
+
64
72
Please ensure that for all contributions, the corresponding documentation is in-sync and up-to-date. All documentation is in English language.
65
73
66
74
Please see [here](https://mercedes-benz.github.io/sechub/latest/sechub-techdoc.html#section-documentation) for details about documentation.
67
75
68
-
69
76
### Commit messages
77
+
70
78
GitHub has the possibility to link commits automatically inside issues when mentioned with #${issue number} inside the commit headline.<br>
71
79
To make things easier to follow/maintain, please always provide commit message in following style:
72
80
73
81
```
74
82
Dedicated short message what was done #${issue number}
75
83
```
84
+
76
85
or
86
+
77
87
```
78
88
Dedicated short message what was done #${issue number}
79
89
80
90
- detail1
81
91
- detail2
82
92
- ...
83
93
```
94
+
84
95
NOTE: Here you MUST add an empty second line between headline and details. It's common practice for GIT.
85
96
86
97
Example:
98
+
87
99
```
88
100
Described commit message format #868
89
101
@@ -92,6 +104,7 @@ Described commit message format #868
92
104
```
93
105
94
106
### Development tools setup
107
+
95
108
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.
96
109
97
110
Please check our [development-setup documentation](https://mercedes-benz.github.io/sechub/latest/sechub-techdoc.html#development-setup) for details.
Copy file name to clipboardexpand all lines: SECURITY.md
-2
Original file line number
Diff line number
Diff line change
@@ -2,5 +2,3 @@
2
2
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.
3
3
4
4
For further Information please visit our [Vulnerability disclosure program](https://www.mercedes-benz.com/en/whitehat/).
Copy file name to clipboardexpand all lines: ide-plugins/vscode/README.md
+1-2
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Recommended: Install the plugin from the Open-VSX marketplace from within [VSCod
15
15
16
16
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.
17
17
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.
19
19
20
20
## Development
21
21
@@ -104,4 +104,3 @@ Please visit https://www.mercedes-benz-techinnovation.com/en/imprint/ for inform
104
104
Notice: Before you use the program in productive use, please take all necessary precautions,
105
105
e.g. testing and verifying the program with regard to your specific use.
106
106
The program was tested solely for our own use cases, which might differ from yours.
0 commit comments