Open
Conversation
EllieKallmier
added
type: documentation
nick-gorman
approved these changes
Mar 2, 2026
Member
nick-gorman
left a comment
nick-gorman
left a comment
There was a problem hiding this comment.
This looks great! Keen to have a go at using these conventions.
| | `type: documentation` | Improvements or additions to documentation | | ||
| | `type: feature` | A new feature or request | | ||
| | `type: question` | Further information is requested | | ||
|
|
Member
There was a problem hiding this comment.
Suggested change
| | `type: technical-debt` | Code could be improved |\ | |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Aims to resolve #3 - setting up project-wide GitHub labelling conventions.
PR contains a md file broadly documenting the decisions made during our workshop on 19/01-20/01 2026 regarding how we want to use labels across the Open ISP GitHub project. The hope is that using a standard labelling schema will make it easier to quickly skim issues and PRs when reviewing the project as a whole, and make filtering more effective and efficient.
I'm not super attached to all the language of these docs, particularly around what the
categorylabel specifically is - I think we can use this label somewhat loosely for the moment and (as discussed) consider adding another keyword (e.g.domain) in future if we find we need more detail.