-
Notifications
You must be signed in to change notification settings - Fork 19
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
contributing: expand issue/PR sections, re-format #186
Conversation
CONTRIBUTING.md
Outdated
|
||
If you have a close to fully fleshed out idea, consider [opening a proposal](https://github.com/Cuprate/cuprate/issues/new/choose). | ||
|
||
Opening a PR with the `A-proposal` tag and writing the proposal in the PR description is also viable. |
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.
Actually, can regular accounts even add labels to their own issues/PRs?
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.
Removing this for now.
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.
I don't think so
Follow up to: #182 (comment)
Submitting an issue
section that describes our issue processTracking issues
sectionPull request title and description
section.github/pull_request_template.md
Preview: https://github.com/hinto-janai/cuprate/blob/contrib/CONTRIBUTING.md
The text inside pull_request_template.md auto-fills the description when creating the PRs, example: https://github.com/hinto-janai/labeler-test/compare/test?expand=1.