Skip to content

Fix typo in advice on unconstrained types#1243

Closed
jjpinto wants to merge 0 commit intogithub:mainfrom
jjpinto:main
Closed

Fix typo in advice on unconstrained types#1243
jjpinto wants to merge 0 commit intogithub:mainfrom
jjpinto:main

Conversation

@jjpinto
Copy link
Copy Markdown
Contributor

@jjpinto jjpinto commented Mar 31, 2026

Fix typo in advice on unconstrained types

Copilot AI review requested due to automatic review settings March 31, 2026 13:00
@jjpinto jjpinto requested a review from aaronpowell as a code owner March 31, 2026 13:00
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the Go instructions documentation to correct a typo in the “Common Pitfalls to Avoid” guidance around unconstrained types, improving clarity and consistency in the writing.

Changes:

  • Fixes “Over-using” → “Overusing” in the unconstrained types pitfall bullet.

@aaronpowell
Copy link
Copy Markdown
Contributor

It looks like you've incorrectly branched from the main branch not staged, and as a result all the materialised plugins are included in this PR.

You can attempt to fix this with a rebase:

git fetch origin staged
git rebase --onto origin/staged origin/main <branch name>
git push --force-with-lease

If that does not resolve it, you can run npm run plugin:clean which will delete the materialised plugins and you can commit that change.

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.

3 participants