-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.23.0 #340
Release 0.23.0 #340
Conversation
Update changelogs and docs
….checkmk into feature-extend-demo-playbooks
RedHat.yml now uses ansible_distribution_file_variety now. Therefor redundany is removed from the code and maybe it works too for other Centos lookalike distributions, like e.g. RockyLinux, Springdate, etc.
These has been used during the change process.
Bumps [actions/stale](https://github.com/actions/stale) from 7 to 8. - [Release notes](https://github.com/actions/stale/releases) - [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md) - [Commits](actions/stale@v7...v8) --- updated-dependencies: - dependency-name: actions/stale dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
How does it work, I think I have followed the described steps, but still get an error |
@msekania you need to post the following statement as a comment here, to confirm, that you agree to the CLA.
|
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. |
one should make readme fro CLA more clear. |
ac89635
to
0e6f27c
Compare
Everyone that was mentioned by the CLA Bot but did not contribute to this PR: I apologize for the inconvenience! I had to perform some git-magic, that went sideways. If you could just sign the CLA real quick, that would be great! For those, where the bot did not find a GitHub account: Please follow the linked guide. That would be: If there are any questions, do let me know. |
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. |
I'm sorry if I'm misunderstanding, you're requesting I sign the CLA in the name of somebody else for the PR to go through even though I have taken no part of this PR? |
If so, the bot will fail if I include any other text than the aforementioned line in the message? As I want to make clear I or my organization have not contributed any work to this push and I have not signed a CLA with this project. |
Hi @Lars and sorry for the misunderstanding. |
I have read the CLA Document and I hereby sign the CLA or my organization already has a signed CLA. |
Hi everyone! Once again apologies for the noise and potential confusion in this PR! See you in roughly two weeks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Most code changes have been reviewed by me when merged into the devel branch.
I just checked the rest of the changes for consistency.
Pull request type
Please check the type of change your PR introduces:
What is the current behavior?
Issue Number:
e.g. #1
What is the new behavior?
Other information