Updated contributing guidelines #282
No reviewers
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#282
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feature/contributing-guidelines"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Updated the README and PR template to help reflect some of our new practices and explain existing processes to new contributors. Should hopefully yield more clarity.
@ -100,7 +100,17 @@ If you need any feature in the api, contact us.<!-- CONTRIBUTING -->I have no idea how I managed to catch this because I suck at spelling and have so many spelling errors in my own projects.... But I believe it should be "noticeable", not "noticable".
@ -100,7 +100,17 @@ If you need any feature in the api, contact us.<!-- CONTRIBUTING -->Good catch!