auxolotl/wiki
20
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Activity

docs: update contributing/formatting/projects

Browse source
This commit is contained in:
Samuel Shuert 2024-05-08 22:45:26 +00:00 committed by Auxolotl Wiki
parent 58722bdb6b
commit fe4aedfab7
1 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
contributing/formatting/projects.md
View file

@ -2,7 +2,7 @@
title: Project Standards title: Project Standards
description: description:
published: true published: true
date: 2024-05-07T23:39:00.653Z date: 2024-05-08T22:45:24.283Z
tags: tags:
editor: markdown editor: markdown
dateCreated: 2024-05-05T21:22:30.441Z dateCreated: 2024-05-05T21:22:30.441Z
@ -30,4 +30,7 @@ All projects should provide:
- **Breaking Changes** should have what it breaks, how it breaks it, and a short transition guide - **Breaking Changes** should have what it breaks, how it breaks it, and a short transition guide
# Merging to main with bugs # Merging to main with bugs
There are a few reasonable expectations for merges, one is that any change that is made in the project should not include bugs except in extremely rare cases where bugs are unable to be fixed without upstream changes. In this case a bug should be added to the projects kanban board (or similar) with relevant information like the file & code section the bug is in and which upstream issue is causing the bug (if known). There are a few reasonable expectations for merges, one is that any change that is made in the project should not include bugs except in extremely rare cases where bugs are unable to be fixed without upstream changes. In this case a bug should be added to the projects kanban board (or similar) with relevant information like the file & code section the bug is in and which upstream issue is causing the bug (if known).
# Code
Autoformat specifications for code can be found on our [Code Standards](https://wiki.auxolotl.org/contributing/formatting/code) page. Please check them there.