Repository navigation
chore(issue_templates): Updates to issue templates - #1711
Merged
Merged
Conversation
… a documentation repo PR Release notes get put in comments on the issue/PR, and labeled accordingly. At that point there is no release note document ready for the upcoming release. So this just adds confusion
This was referenced Oct 20, 2026
NickLarsenNZ
marked this pull request as ready for review
October 20, 2026 11:50
NickLarsenNZ
enabled auto-merge
October 20, 2026 11:50
NickLarsenNZ
changed the title
Techassi
moved this from Development: Waiting for Review
to Development: In Review
in Stackable Engineering
Techassi
approved these changes
Oct 20, 2026
Techassi
moved this from Development: In Review
to Development: Done
in Stackable Engineering
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
4 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.
Release notes get put in comments on the issue/PR, and labeled accordingly. At that point there is no release note document ready for the upcoming release. So this just adds confusion.
Vector in Jenkins had not been updated in a long time.