-
Notifications
You must be signed in to change notification settings - Fork 740
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
Update contribution documents #8382
Conversation
- Reflect true attribution practices - Reflect true merge process (this changed a long time ago)
We have almost never used these and serve as a source of confusion for new contributors.
Caught in a bad regex
Every function includes the `script_component.hpp` file on the first line. Any additional includes or defines must be below this include. | ||
|
||
All code written must be below this include and any potential additional includes or defines. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
additional includes or defines
Duplicated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought the same, but think it's just badly worded. Code must appear below all includes and defines.
Includes and defines must appear below the script component include.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I guess so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This whole document could probably use a once over separately. I just spotted the outdated info while doing this. 👍
Co-authored-by: jonpas <[email protected]>
The people responsible for merging changes to existing addons are the maintainers listed in the README.md file of the respective addon folder. | ||
#### Merge Criteria | ||
|
||
All pull requests must receive approval from a maintainer and must pass all required continuous integration checks before they can be merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be members
instead of maintainers
now?
|
||
#### New Addons / Other Changes | ||
If a pull request adds a new addon, or changes something else, like the README, everyone has 72 hours to comment on the changes. After that, one of the project leads will merge it. | ||
Non-trivial pull requests should ideally be thouroughly reviewed by multiple maintainers or at least one maintainer highly familiar with any code modified. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same
* Update code guidelines for script_component * Update contributing documents for pull requests - Reflect true attribution practices - Reflect true merge process (this changed a long time ago) * Remove listed maintainer from component readmes We have almost never used these and serve as a source of confusion for new contributors.
When merged this pull request will: