Thank you for taking the time to contribute to Eirini. You can find more information about the project at:
- #eirini-dev slack channel.
- PivotalTracker show our current backlog and what we have planned for the near future.
- CI pipeline
- Project page
We use PivotalTracker to track bugs and a story is automatically created when you submit an issue on GitHub.
Pull requests are the best way to propose changes to the codebase. When a Pull request is submitted, a story is automatically created in the Icebox in our PivotalTracker.
- Sign and submit the appropriate individual or corporate CLA
- Fork this project into your GitHub organisation or username
- Clone your fork on your local machine
- Make sure you are up-to-date with the upstream
master
branch - Create your feature branch
- Commit your changes on your feature branch
- Run tests and static checks
- Deploy your patched version of Eirini in your cluster if needed
- Push your feature branch to your fork
- Issue a Pull request
Before you submit a Pull request, you must make sure that your contribution meets the following requirements:
- Your change has been well covered by unit tests (if applicable)
- All tests are passing
- All static code checks are passing. We enforce that by using golangci-lint
You can check all that by executing the following script:
$ ./scripts/check-everything.sh
Our test scripts depend on telepresence
, kind
, and skaffold
.