Skip to content

Conversation

@DebakelOrakel
Copy link
Contributor

@DebakelOrakel DebakelOrakel commented Feb 28, 2024

Checklist

  • The PR has a meaningful title. It will be used to auto-generate the
    changelog.
    The PR has a meaningful description that sums up the change. It will be
    linked in the changelog.
  • PR contains a single logical change (to build a better changelog).
  • Update the documentation.
  • Categorize the PR by adding one of the labels:
    bug, enhancement, documentation, change, breaking, dependency
    as they show up in the changelog.
  • Link this PR to related issues or PRs.

@DebakelOrakel DebakelOrakel added the breaking Breaking Changes label Feb 28, 2024
@DebakelOrakel DebakelOrakel requested a review from a team as a code owner February 28, 2024 13:33
@DebakelOrakel DebakelOrakel force-pushed the feat/lokistack-as-default branch from 1d5f194 to 51db08d Compare February 28, 2024 13:34
@DebakelOrakel DebakelOrakel merged commit 50ec9ec into master Mar 1, 2024
@DebakelOrakel DebakelOrakel deleted the feat/lokistack-as-default branch March 1, 2024 10:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking Breaking Changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants