-
Notifications
You must be signed in to change notification settings - Fork 37
Update contributor's guide #502
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
Conversation
Co-authored-by: Johannes Schmölder <[email protected]>
Co-authored-by: Johannes Schmölder <[email protected]>
|
Generally looks good. Should we start tracking the individual tasks from the (e.g. linting / auto-formatting) here or make separate issues? See also #404 |
|
I think the linting, formatting is an issue on its own, ive added a todo to add this to the |
|
Gotcha. For reference, here is the CADET-Process Contributor's guide. I'm quite happy with how it turned out. But note, we don't have a real developer's guide so it has double duty here. But I'm also not entirely sure yet where exactly the difference (although there certainly is one). |
|
Thanks! Ive added the PR vs issue and branch policy sections. The rest is either already documented in the dev-guide (and i want to avoid repetition), or missing (formatting, pre-commit). |
lieres
left a comment
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.
Consider mentioning "private" mail to [email protected] as additional contact option.
as per https://github.com/cadet/CADET-Project-Management/issues/91