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 typos in comment. #2009

Merged
merged 1 commit into from
Dec 11, 2022
Merged

Fix typos in comment. #2009

merged 1 commit into from
Dec 11, 2022

Conversation

Jarod42
Copy link
Contributor

@Jarod42 Jarod42 commented Dec 11, 2022

What does this PR do?

Just fix typo in comment

How does this PR change Premake's behavior?

No code change.

Anything else we should know?

No.

Did you check all the boxes?

  • Focus on a single fix or feature; remove any unrelated formatting or code changes
  • Add unit tests showing fix or feature works; all tests pass
  • Mention any related issues (put closes #XXXX in comment to auto-close issue when PR is merged)
  • Follow our coding conventions
  • Minimize the number of commits
  • Align documentation to your changes

Copy link
Member

@KyrietS KyrietS left a comment

Choose a reason for hiding this comment

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

That's impressive! Did you run the source code through a dictionary check or something? I hope you didn't just spend the evening carefully reading all the comments 😄

@KyrietS KyrietS merged commit ac8ba36 into premake:master Dec 11, 2022
@Jarod42 Jarod42 deleted the typos branch December 11, 2022 17:06
@Jarod42
Copy link
Contributor Author

Jarod42 commented Dec 11, 2022

@KyrietS : I have a plugin which checks that... I have to do some validations though... :)

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