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
Copy file name to clipboardExpand all lines: README.md
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,11 @@ Detailed build and testing instructions can be found in [BUILDANDTEST.md](./BUIL
46
46
47
47
Troubleshooting: If you run into issues, please open an [issue](https://github.com/finos/rune-python-generator/issues). This helps us improve the guide for everyone.
48
48
49
+
### Coding Standards
50
+
51
+
- Indentation: Since Python is sensitive to indentation, ensure your submission uses four spaces for each indentation instead of tabs.
52
+
- Java vs xTend: since the intention is to replace xTend, all new code should be written in Java. Ideally, changes to existing code will migrate xTend code to Java.
53
+
49
54
### 1. Building with Maven
50
55
51
56
Start by cloning the project: `git clone https://github.com/finos/rune-python-generator`
@@ -109,7 +114,9 @@ We welcome contributions! Please follow these steps to get started:
109
114
3. Read our [contribution guidelines](.github/CONTRIBUTING.md) and [Community Code of Conduct](https://www.finos.org/code-of-conduct)
110
115
4. Commit your changes (`git commit -am 'Add some fooBar'`)
111
116
5. Push to the branch (`git push origin feature/fooBar`)
112
-
6. Create a new Pull Request
117
+
6. Create a new Pull Request: the intention is to ensure that Main is always production ready and matches a release.
118
+
- Simple / short running changes : the PR should be to Main
119
+
- Complex / long running changes: the recommendation is to complete all the changes in a staging branch, such as Develop or another branch of your choosing. Once the change is complete and passes all tests, then raise the PR to main from your staging branch.
113
120
114
121
**NOTE: FINOS repositories require an executed and active FINOS Individual Contributor License Agreement (ICLA) or an executed and active FINOS Corporate Contribution License Agreement (CCLA). The FINOS Clabot tool (or EasyCLA) will flag and block commits from individuals not covered. Please note that some CCLAs require individuals/employees to be explicitly named on the CCLA.**
0 commit comments