-
Notifications
You must be signed in to change notification settings - Fork 593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CONTRIBUTING.md #5042
CONTRIBUTING.md #5042
Conversation
tiloKo
commented
Sep 10, 2024
•
edited
Loading
edited
- create new CONTRIBUTING.md in root folder
- delete old one in .github subfolder
- adopted links (README.md, docs)
- moved development related content from old CONTRIBUTING.md (mainly for groovy development) to DEVELOPMENT.md
- moved DEVELOPMENT.md into the documentation subfolder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great, thanks for that! Let's add the https://github.com/SAP/.github/blob/main/CONTRIBUTING_USING_GENAI.md document as well and fix the reference link.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the reason of moving this? If you don't mind, please leave it in .github
folder to declutter the root directory. I would rather move the DEVELOPMENT.md
file there as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also one cannot really see what has changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Obviously the OSPO did not find the file
- A folder starting with a dot is in some environments considered hidden
- Contribution is some key element of an os project, so imho it is important enough to put in in the root directory
- I would agree to move the DEVELOPMENT.md in the documentation folder
- I do not see any relation or dependency between github and contribution which is implied if the file is put in a subdirectory of this name.
https://mozillascience.github.io/working-open-workshop/contributing/
"CONTRIBUTING.md should be in your root directory"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. @CCFenner Is it ok with you?
/it |
9ef7a1f
to
79e5728
Compare
Quality Gate passedIssues Measures |
I did all the changes once more but for moving the file I used git mv command.
|
/it |
* origin/master: (35 commits) feat(notification): Notify in case of Release failure (SAP#5045) fix(docs): remove dead links (SAP#5051) chore: remove obsolete cloud sdk conversion file (SAP#5036) feat: fail if script is not found in package.json file (SAP#5029) feat(sonar): Enable trustengine for token retrieval (SAP#5046) feat(trustengine): Add new resource reference to parameter docs generation (SAP#5038) docs: add unit test tags flag (SAP#4947) CONTRIBUTING.md (SAP#5042) addon.yml may now contain wildCard MAXX (SAP#5039) fix(codeqlExecuteScan): handle spaces in path to maven settings file (SAP#5037) feat(trustengine): Integrate Trust Engine into step config resolver (SAP#5032) fix(http): Use configured logger for retryClient (SAP#5040) Updated helm.sh/helm from 13.14.0 to 13.14.2 (SAP#5041) Copy full project (SAP#5033) feat(vault): support complex data types in secrets (SAP#5006) Added pagination logic for retrieving projects from Black Duck server (SAP#5031) Update aws deps (SAP#5034) Add possible values and default (SAP#5030) Fix security issues reported by Black Duck (SAP#5014) Exposing build artifact metadata from maven and npm (SAP#5008) ...
…fig-fix * origin/master: (35 commits) feat(notification): Notify in case of Release failure (SAP#5045) fix(docs): remove dead links (SAP#5051) chore: remove obsolete cloud sdk conversion file (SAP#5036) feat: fail if script is not found in package.json file (SAP#5029) feat(sonar): Enable trustengine for token retrieval (SAP#5046) feat(trustengine): Add new resource reference to parameter docs generation (SAP#5038) docs: add unit test tags flag (SAP#4947) CONTRIBUTING.md (SAP#5042) addon.yml may now contain wildCard MAXX (SAP#5039) fix(codeqlExecuteScan): handle spaces in path to maven settings file (SAP#5037) feat(trustengine): Integrate Trust Engine into step config resolver (SAP#5032) fix(http): Use configured logger for retryClient (SAP#5040) Updated helm.sh/helm from 13.14.0 to 13.14.2 (SAP#5041) Copy full project (SAP#5033) feat(vault): support complex data types in secrets (SAP#5006) Added pagination logic for retrieving projects from Black Duck server (SAP#5031) Update aws deps (SAP#5034) Add possible values and default (SAP#5030) Fix security issues reported by Black Duck (SAP#5014) Exposing build artifact metadata from maven and npm (SAP#5008) ...
…ix-fix * origin/master: (35 commits) feat(notification): Notify in case of Release failure (SAP#5045) fix(docs): remove dead links (SAP#5051) chore: remove obsolete cloud sdk conversion file (SAP#5036) feat: fail if script is not found in package.json file (SAP#5029) feat(sonar): Enable trustengine for token retrieval (SAP#5046) feat(trustengine): Add new resource reference to parameter docs generation (SAP#5038) docs: add unit test tags flag (SAP#4947) CONTRIBUTING.md (SAP#5042) addon.yml may now contain wildCard MAXX (SAP#5039) fix(codeqlExecuteScan): handle spaces in path to maven settings file (SAP#5037) feat(trustengine): Integrate Trust Engine into step config resolver (SAP#5032) fix(http): Use configured logger for retryClient (SAP#5040) Updated helm.sh/helm from 13.14.0 to 13.14.2 (SAP#5041) Copy full project (SAP#5033) feat(vault): support complex data types in secrets (SAP#5006) Added pagination logic for retrieving projects from Black Duck server (SAP#5031) Update aws deps (SAP#5034) Add possible values and default (SAP#5030) Fix security issues reported by Black Duck (SAP#5014) Exposing build artifact metadata from maven and npm (SAP#5008) ...