Definitions - duonl/bcld GitHub Wiki

GitHub Issues can display two status definitions:

Both definitions have some requirements.

⚙️ Open

Open issues must be refined to the point where development can begin.
Issues that are currently under development stay open.
If an issue is currently open, the responsible developer MUST keep the issue updated, using either updated descriptions or comments.
The issue must be assigned to a responsible developer.
Review each other's issues.
Take your time and be careful.
Try to fix one issue at a time.
Don't forget to assign labels.
During development, fixes can gradually be rolled out, using the develop child branches.
Every change to a branch triggers the GitHub Workflow.
All changes must be tested successfully before an issue can be closed.

Issues can only be closed once the GitHub Workflow has been completed.
This ensures that all tests have finished successfully.
At least one other member has reviewed the code changes and the issue.
If an issue has been closed, the changes may be merged to the main branch.
This will trigger the final tests.
An issue may also be closed if it cannot be fixed or cannot be reproduced.
If an issue has been stale for too long, the issue may also be closed.
An issue may also be closed if it is irrelevant, obsolete, or superseded.