Add a continuous integration category #92
Merged
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
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.
In the jupyterhub organization I've often ended up labelling PRs with a
cilabel and/or prefixed the title withci, to then list such PRs underContinuous integration improvements.I think there is a point of distinguishing this category from the maintenance category, because we quite often need to make changes to .github/workflows/test.yaml or similar, but they are often not relevant to think about like another maintenance PR touching the actual code of the project.
I often find myself reading changelogs list of PRs to find what could possibly have caused a bug I'm observing, but the bugs shouldn't have been caused by a CI change typically, so if they are listed separately that is helpful for example.