#Osquery slack code

This CONTRIBUTING guide focuses more on concepts and high level workflow. Office hours are announced on our Slack on the #officehours channel.įor documentation on building, testing, and formatting code, please review the ReadTheDocs article on building osquery. The osquery team also hosts regular office hours where the community is invited to discuss osquery development with the core team.

#Osquery slack code

Note: prefer to keep discussion about code changes in the GitHub pull request thread. The #code-review Slack channel has been set up to handle urgent review needs as well as questions about your PR. Feel free to register using the following shared invite. If you need help, both the core team and community members are on the osquery Slack. You can see who the core team is by viewing the team page on the osquery GitHub organization.

After being reviewed by the core team and tested by CI, if all is well, they will be pushed to master and the corresponding PR closed. Please read these guidelines before submitting your code as they are designed to save you time later on when your code is under review.Īll contributions are submitted via pull requests (PRs) open against the osquery's master branch on GitHub. These guidelines explain the basics of the osquery development process and how you can contribute. We want to make contributing to osquery as simple and transparent as possible.