Skip to content

Commit f4e60f5

Browse files
committed
Merge branch 'devel' of https://github.com/redhat-cop/tower_configuration into devel
2 parents 4d59d91 + aa4aa09 commit f4e60f5

File tree

2 files changed

+6
-5
lines changed

2 files changed

+6
-5
lines changed

.github/CONTRIBUTING.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,10 +29,11 @@ If you feel like getting your hands dirty, feel free to make the change yourself
2929
2. Create a branch named appropriately for the change you are going to make.
3030
3. Make your code change.
3131
4. If you are creating a new role, please add a test for it in our [testing playbook.](https://github.com/redhat-cop/tower_configuration/blob/devel/playbooks/example_with_yaml/configure_tower.yml) by adding a new role entry and adding the appropriate yaml file with test data in the tower_configs directory.
32-
5. Push your code change up to your forked repo.
33-
6. Open a Pull Request to merge your changes to this repo. The comment box will be filled in automatically via a template.
34-
7. All Pull Requests will be subject to Ansible and Yaml Linting checks. Please make sure that your code complies and fix any warnings that arise. These are Checks that apear at the bottom of your Pull Request.
35-
8. All Pull requests are subject to Testing against being used in tower. As above there is a check at the bottom of your pull request for this named integration.
32+
5. Add a changelog fragment in `changelogs/fragments` as per https://docs.ansible.com/ansible/latest/community/development_process.html#changelogs
33+
6. Push your code change up to your forked repo.
34+
7. Open a Pull Request to merge your changes to this repo. The comment box will be filled in automatically via a template.
35+
8. All Pull Requests will be subject to Ansible and Yaml Linting checks. Please make sure that your code complies and fix any warnings that arise. These are Checks that apear at the bottom of your Pull Request.
36+
9. All Pull requests are subject to Testing against being used in tower. As above there is a check at the bottom of your pull request for this named integration.
3637

3738
See [Using Pull Requests](https://help.github.com/articles/using-pull-requests/) got more information on how to use GitHub PRs.
3839

changelogs/config.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,6 @@ sections:
2727
- Bugfixes
2828
- - known_issues
2929
- Known Issues
30-
title: Redhat_Cop.Tower_Configuration
30+
title: redhat_cop.tower_configuration
3131
trivial_section_name: trivial
3232
use_fqcn: true

0 commit comments

Comments
 (0)