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

Encourage contributors to align the docs #1609

Merged
merged 1 commit into from
Apr 4, 2021

Conversation

KyrietS
Copy link
Member

@KyrietS KyrietS commented Apr 3, 2021

What does this PR do?

Premake has evolved over the years, but its documentation has not kept up with the changes. Even now there are a few pending PRs introducing new features, flags and options but none of them would be mentioned in our docs after merge. Since contributing to the docs is possible now, I'd like to see people improving Premake along with its documentation.

This PR introduces a new box for every Pull Request:

How does this PR change Premake's behavior?

No changes in behaviour

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

You can now support Premake on our OpenCollective. Your contributions help us spend more time responding to requests like these!

Copy link
Member

@starkos starkos left a comment

Choose a reason for hiding this comment

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

Nice, thanks!

@starkos starkos merged commit 86fa698 into premake:master Apr 4, 2021
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.

None yet

2 participants