Issue usage info #43
Merged
Issue usage info #43
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
June 20, 2022 22:00
Signed-off-by: Flurb <private@tjalma.com>
Signed-off-by: Flurb <private@tjalma.com>
dlabordus
approved these changes
Jun 21, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposal how to use issues / pull requests.
If accepted, we can implement it on all repositories.
Labels is already explained quite well in the Pull Requests section.
For issues I propose to use an issue template.
When an issue is created, it's added to the
To docolumn of the specific repository.After the refinement of that issue, it's being moved to the
Ready for developmentcolumn (which must be added).This takes away to usage of the labels
Refinement neededandRefinement donefor example, which is AND more work AND sensitive for mistakes.Closes #7