-
Notifications
You must be signed in to change notification settings - Fork 71
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
chore(meta): Create issue templates and PR template, add authors.md #835
base: main
Are you sure you want to change the base?
Conversation
To make it easier for the users and us to understand what is happening and why, and what the preconditions are.
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
Signed-off-by: simonsan <[email protected]>
Added note to search our external docs as well, before opening an issue. |
Could you give it a rough look, @aawsome because I'm unsure if the direction is fine? Thanks a lot! |
What about the other (existing) authors which already contributed to the project? |
When added, we can open an issue and tag them to please leave their name, would be my proposal. But at some point we might want to start? Better late than never kind of style |
Note for us (taken from |
Hello !
Let me know what you think about this! |
To make it easier for the users and us to understand what is happening and why, and what the preconditions are.
The rendered issue form template can be seen here:
https://github.com/rustic-rs/rustic/blob/simonsan-patch-1/.github/ISSUE_TEMPLATE/bug_report.yml
The rendered feature request form template can be seen here:
https://github.com/rustic-rs/rustic/blob/simonsan-patch-1/.github/ISSUE_TEMPLATE/feature_request.yml
Blocked by: Needs adoption to rustic_core extraction to own repository. No choice needed in templates.