Skip to content

Conversation

@leonelquinteros
Copy link
Owner

Before creating your Pull Request...

  • New Pull Requests should include a good description of what's being merged.
  • Ideally, all Pull Requests are preceded by a discussion initiated in an Issue on this repository.
  • For bug fixes is mandatory to have tests that cover and fail when the bug is present and will pass after this Pull Request.
  • For changes and improvements, new tests have to be provided to cover the new features.

Is this a fix, improvement or something else?

...

What does this change implement/fix?

...

I have ...

  • answered the 2 questions above,
  • discussed this change in an issue,
  • included tests to cover this changes.

@leonelquinteros leonelquinteros merged commit 5aa198b into master Mar 18, 2025
4 checks passed
@leonelquinteros leonelquinteros deleted the function-type-extractor branch March 18, 2025 18:07
Copy link

@TateGunning TateGunning left a comment

Choose a reason for hiding this comment

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

Committing respectfully to see if it's a go, thank you..

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants