Repository navigation
process: Python Coding Guidelines - #741
Conversation
License Check Results🚀 The license check preparation job ran successfully. Status: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
masc2023
left a comment
There was a problem hiding this comment.
Please consider to move this content outside of process folder, as it contains concrete tools for a specific language. Process area should not be tool agnostic.
|
hoe-jo
left a comment
There was a problem hiding this comment.
Please take a look a the comments
masc2023
left a comment
There was a problem hiding this comment.
Can we add a placeholder for the RUSt guidelines?
|
mhh seems I merged the wrong main :D |
masc2023
left a comment
There was a problem hiding this comment.
My aspects, location, structure covered now
|
I have currently no idea what that is about, so I cannot merge 😢 https://api.eclipse.org/git/eca/status/gh/eclipse-score/score/741 |
Just follow our Git guidelines, may also squash it to one commit, the other I do not know |
|
All eca checks were failing in eclipse-score. Fixed now. |
hoe-jo
left a comment
There was a problem hiding this comment.
Link to Writing Test Cases still missing, can be added in later PR
Rest ok
Move guidelines to contribution and add guidelines for python
Move guidelines to contribution and add guidelines for python
Python Guidelines based on #416
@hoe-jo I would like to clarify some formal points before we discuss the actual guidelines: