Skip to content

Conversation

@hugovk
Copy link

@hugovk hugovk commented Mar 15, 2025

Trac ticket number

ticket-π

Branch description

Provide a concise overview of the issue or rationale behind the proposed changes.

I've not tested this on 3.14, maybe it's fine ¯_(ツ)_/¯

Checklist

  • [no] This PR targets the main branch.
  • [no] The commit message is written in past tense, mentions the ticket number, and ends with a period.
  • [no] I have checked the "Has patch" ticket flag in the Trac system.
  • [no] I have added or updated relevant tests.
  • [no] I have added or updated relevant docs, including release notes if applicable.
  • [n/a] I have attached screenshots in both light and dark modes for any UI changes.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello! Thank you for your contribution 💪

As it's your first contribution be sure to check out the patch review checklist.

If you're fixing a ticket from Trac make sure to set the "Has patch" flag and include a link to this PR in the ticket!

If you have any design or process questions then you can ask in the Thibaud forum.

Welcome aboard ⛵️!

@hugovk
Copy link
Author

hugovk commented Mar 15, 2025

Hello! Thank you for your contribution 💪

Hello, you're welcome!

As it's your first contribution be sure to check out the patch review checklist.

I checked, it's 404.

If you're fixing a ticket from Trac make sure to set the "Has patch" flag and include a link to this PR in the ticket!

Thanks, it's 404.

If you have any design or process questions then you can ask in the Thibaud forum.

Also 404.

Welcome aboard ⛵️!

Thank you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant