Contributing
Issues
Request features and report bugs using the GitHub Issue Tracker.
Please indicate the platform you are using fsnotify on.
A code example to reproduce the problem is appreciated.
Pull Requests
Contributor License Agreement
fsnotify is derived from code in the golang.org/x/exp package and it may be included in the standard library in the future. Therefore fsnotify carries the same LICENSE as Go. Contributors retain their copyright, so you need to fill out a short form before we can accept your contribution: Google Individual Contributor License Agreement.
Please indicate that you have signed the CLA in your pull request.
How fsnotify is Developed
Development is done on feature branches.
Tests are run on BSD, Linux, macOS and Windows.
Pull requests are reviewed and [applied to master][am] using [hub][].
Maintainers may modify or squash commits rather than asking contributors to.
To issue a new release, the maintainers will:
Update the CHANGELOG
Tag a version, which will become available through gopkg.in.
How to Fork
For smooth sailing, always use the original import path. Installing with go get makes this easy.
Install from GitHub (
go get -u github.com/fsnotify/fsnotify)Create your feature branch (
git checkout -b my-new-feature)Ensure everything works and the tests pass (see below)
Commit your changes (
git commit -am 'Add some feature')
Contribute upstream:
Fork fsnotify on GitHub
Add your remote (
git remote add fork git@github.com:mycompany/repo.git)Push to the branch (
git push fork my-new-feature)Create a new Pull Request on GitHub
This workflow is thoroughly explained by Katrina Owen.
Testing
fsnotify uses build tags to compile different code on Linux, BSD, macOS, and Windows.
Before doing a pull request, please do your best to test your changes on multiple platforms, and list which platforms you were able/unable to test on.
Maintainers
Help maintaining fsnotify is welcome. To be a maintainer:
Submit a pull request and sign the CLA as above.
You must be able to run the test suite on Mac, Windows, Linux and BSD.
All code changes should be internal pull requests.
Releases are tagged using Semantic Versioning.
Last updated