Lumberjack
WebsiteRareloopTimber DocumentationTwig Documentation
v6
v6
  • Introduction
  • What's New
  • Upgrade Guide
  • Getting Started
    • Installation
    • Configuration
  • The Basics
    • Lifecycle
    • Routing
    • WordPress Controllers
    • Post Types
    • Query Builder
    • View Models
    • HTTP Requests
    • HTTP Responses
    • Middleware
    • Sessions
    • Helpers
    • Collections
  • Container
    • Using the Container
    • Service Providers
    • Facades
  • Misc
    • Contributing
    • Notable Mentions
    • Code of Conduct
    • View on GitHub
    • View Docs on GitHub
    • Submit an issue
Powered by GitBook
On this page
  • Pull Requests
  • Running Tests
  • Linting against PSR2 Coding Standards
  1. Misc

Contributing

PreviousFacadesNextNotable Mentions

Last updated 2 years ago

Contributions are welcome and will be fully credited.

We accept contributions via Pull Requests on .

Pull Requests

  • - The easiest way to apply the conventions is to install .

  • Add tests - Your patch likely will not be accepted if it doesn't have tests.

  • Create feature branches - Don't ask us to pull from your master branch.

  • One pull request per feature or fix - If you want to do more than one thing, send multiple pull requests.

  • Send coherent history - Make sure each individual commit in your pull request is meaningful. If you had to make multiple intermediate commits while developing, please before submitting. We follow the advice of Chris Beams on .

Running Tests

$ vendor/bin/phpunit

Linting against PSR2 Coding Standards

$ vendor/bin/phpcs --standard=PSR2 ./src
Github
PSR-2 Coding Standard
PHP Code Sniffer
squash them
How to write good commit messages