First off, thank you for considering contributing to rundeck-zabbix 🎉. Following these guidelines help to communicate that you respect the time of the developers managing and developing this open source project. In return, they should reciprocate that respect in addressing your issue, assessing changes, and helping you finalise your pull requests.
If you've noticed a bug or have a question, search the issue tracker to see if someone else has already created a ticket. If not, go ahead and make one!
If this is something you think you can fix, then fork rundeck-zabbix and create a branch with a descriptive name.
A good branch name would be (where issue #225 is the ticket you're working on):
git checkout -b 225-add-responseRefer to the dev setup guide.
At this point, you're ready to make your changes! Feel free to ask for help; everyone is a beginner at first.
This project uses go modules to manage dependencies.
Running make test runs tests.
Also, remember to write tests 😸 We care about quality, so your PR won't be merged until all tests pass.
If a maintainer asks you to "rebase" your PR, they're saying that a lot of code has changed, and that you need to update your branch so it's easier to merge.
A PR can only be merged into master by a maintainer if:
- It is passing CI.
- It has no requested changes.
- It is up to date with current master.
Any maintainer is allowed to merge a PR if all of these conditions are met.
Releases are done on the Github UI using SemVer for versioning.