Skip to content

Conversation

@Jarod42
Copy link
Contributor

@Jarod42 Jarod42 commented Jan 11, 2025

What does this PR do?

Improve some documentation

How does this PR change Premake's behavior?

No changes

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

`value` one of:
* `on` - needs documentation.
* `off` - needs documentation.
* `on` - generated file should be compiled.
Copy link
Member

Choose a reason for hiding this comment

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

General thought: We have a mix between "on"/"off" and "On"/"Off" throughout the docs. Should we normalize the documentation to one or the other?

@nickclark2016 nickclark2016 merged commit 20ee427 into premake:master Jan 22, 2025
49 checks passed
@Jarod42 Jarod42 deleted the docs branch January 22, 2025 15:29
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