gitea-admin
/
ansible-roles
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
collection of ansible roles
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
18 Commits
1 Branch
0 Tags
422 KiB
 
 
 
 
Tag: Branch: Tree: ad7d8ba2ac
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'ad7d8ba2ac'
${ noResults }
ansible-roles/needs_refactoring/icinga2/icinga2/CONTRIBUTING.md

1.5 KiB
Raw Blame History

Contributing

A roadmap of this project is located at https://github.com/Icinga/ansible-icinga2/milestones. Please consider this roadmap when you start contributing to the project.

Before starting your work on this module, you should fork the project to your GitHub account. This allows you to freely experiment with your changes. When your changes are complete, submit a pull request. All pull requests will be reviewed and merged if they suit some general guidelines:

  • Changes are located in a topic branch
  • For new functionality, proper tests are written
  • Changes should not solve certain problems on special environments
  • Your change does not handle third party software for which dedicated Ansible role exist
    • such as creating databases, installing webserver etc.

Branches

Choosing a proper name for a branch helps us identify its purpose and possibly find an associated bug or feature. Generally a branch name should include a topic such as fix or feature followed by a description and an issue number if applicable. Branches should have only changes relevant to a specific issue.

git checkout -b fix/service-template-typo-1234
git checkout -b feature/config-handling-1235

Testing

If you add new functionality, make sure to write appropriate tests as well. A complete guide on how to run tests is described in TESTING.md.