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

fix: Could not parse JSON #174

Merged
merged 1 commit into from
Dec 31, 2024
Merged

fix: Could not parse JSON #174

merged 1 commit into from
Dec 31, 2024

Conversation

kurosakishigure
Copy link
Owner

Description

  • What is the purpose of this PR?
  • What problem does it solve?
  • Are there any breaking changes or backwards compatibility issues?

Related Issue

Type of Change

  • Bug fix

How Has This Been Tested?

  • I have run unit tests
  • I have tested the changes manually
  • I have tested in a staging environment

Checklist

  • I have read and followed the guidelines in CONTRIBUTING.md
  • I have already updated the related templates accordingly (if applicable)
  • I have written or updated relevant documentation (if applicable)
  • I have added or updated tests to cover my changes (if applicable)
  • I have reviewed my code for any potential issues

Additional Notes

@github-actions github-actions bot added the bug Fix issue label Dec 31, 2024
@kurosakishigure kurosakishigure merged commit b2e57bf into canary Dec 31, 2024
24 checks passed
@kurosakishigure kurosakishigure deleted the fix/workflows_triage branch December 31, 2024 09:05
@github-actions github-actions bot added the locked Lock threads label Jan 15, 2025
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Fix issue locked Lock threads
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant