984
edits
Changes
Jump to navigation
Jump to search
Line 24:
Line 24: − + + +
+ branch name
# if not already done, '''open an issue''' on Github to explain the problem you want to solve or the functionality you want to work on.
# if not already done, '''open an issue''' on Github to explain the problem you want to solve or the functionality you want to work on.
# if you want to work on an existing issue, '''tell everyone in the issue's Github comments'''.
# if you want to work on an existing issue, '''tell everyone in the issue's Github comments'''.
# fork the project and '''create one branch per issue or functionality you want to work on'''. When you're ready to propose something, send a "pull request"; be patient, sometimes it takes time to the core team to review pull request.
# fork the project and '''create one branch per issue or functionality you want to work on'''.
## It's cool to name it ''issue/[issue_number]-[name]'', ex.: ''issue/1630-name-of-the-issue''
## When you're ready to propose something, send a "pull request"; be patient, sometimes it takes time to the core team to review pull request.
# '''coding style''' is defined in the .editorconfig file, see [https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig]; many editors support EditorConfig, check yours: https://editorconfig.org
# '''coding style''' is defined in the .editorconfig file, see [https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig https://github.com/openfoodfacts/openfoodfacts-server/blob/master/.editorconfig]; many editors support EditorConfig, check yours: https://editorconfig.org