CUMULUS-4436: Adding initial best practices information for languages and adding tasks #4188
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary: Summary of changes
Addresses CUMULUS-4436: Update Cumulus documentation on Python and tasks
Changes
docs/development/python-best-practices.mdto capture Python language expectations, tooling, and standards.docs/development/typescript-best-practices.mdto capture Typescript language expectations, tooling and standards. Content from this was pulled from various cumulus docs.docs/development/quality-and-coverage.mdfile to reference the "best practice language docs" and provide a higher level repo management explanation of tooling and usage.docs/adding-a-task.mdto provide overview and expectations for creating a task.website/sidebar.jsto include new "best practices" documents.PR Checklist
📝 Note:
For most pull requests, please Squash and merge to maintain a clean and readable commit history.