Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BE: Chore: Drop messages v1 #633

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

BE: Chore: Drop messages v1 #633

wants to merge 2 commits into from

Conversation

Haarolean
Copy link
Member

  • Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Resolves #211
Is there anything you'd like reviewers to focus on?

How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

  • No need to
  • Manually (please, describe, if necessary)
  • Unit checks
  • Integration checks
  • Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
  • My changes generate no new warnings (e.g. Sonar is happy)
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Check out Contributing and Code of Conduct

A picture of a cute animal (not mandatory but encouraged)

@Haarolean Haarolean added scope/frontend Related to frontend changes scope/backend Related to backend changes type/chore Boring stuff, could be refactoring or tech debt area/messages labels Oct 24, 2024
@Haarolean Haarolean self-assigned this Oct 24, 2024
@Haarolean Haarolean requested review from a team as code owners October 24, 2024 09:58
@kapybro kapybro bot added status/triage Issues pending maintainers triage status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Oct 24, 2024
@Haarolean Haarolean added hacktoberfest-accepted PRs accepted towards hacktoberfest goal and will be counted as approved and removed status/triage/completed Automatic triage completed labels Oct 24, 2024
@Haarolean Haarolean marked this pull request as draft December 9, 2024 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/messages hacktoberfest-accepted PRs accepted towards hacktoberfest goal and will be counted as approved scope/backend Related to backend changes scope/frontend Related to frontend changes type/chore Boring stuff, could be refactoring or tech debt
Projects
None yet
Development

Successfully merging this pull request may close these issues.

BE: Nuke Messages v1 API
1 participant