Init

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# default owners
+*   @stoe

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/

.github/CONTRIBUTING.md

@@ -0,0 +1,28 @@
+## Contributing
+
+[fork]: https://github.com/stoe/actions/fork
+[pr]: https://github.com/stoe/actions/compare
+[code-of-conduct]: CODE_OF_CONDUCT.md
+
+Hi there! I'm thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+
+## Submitting a pull request
+
+1. [Fork][fork] and clone the repository
+1. Create a new branch: `git checkout -b my-branch-name`
+1. Make your change
+1. Push to your fork and [submit a pull request][pr]
+1. Pat your self on the back and wait for your pull request to be reviewed and merged.
+
+Here are a few things you can do that will increase the likelihood of your pull request being accepted:
+
+- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
+- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+Work in Progress pull request are also welcome to get feedback early on, or if there is something blocked you.
+
+## Resources
+
+- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
+- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
+- [GitHub Help](https://help.github.com)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,32 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - Version [e.g. 22]
+
+
+**Shell (please complete the following information):**
+ - Type: [e.g. bash, zsh]
+ - Terminal: [e.g. native, iTerm, hyper]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,17 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,10 @@
+Fixes #
+
+Changes is in this PR
+-
+-
+
+Have you ...
+- [ ] followed the guidelines in our [Contributing](./CONTRIBUTING.md) document?
+
+cc/ @stoe

.github/stale.yml

@@ -0,0 +1,20 @@
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 30
+
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 7
+
+# Issues with these labels will never be considered stale
+exemptLabels: '🤖 backlog'
+
+# Label to use when marking an issue as stale
+staleLabel: '🤖 stale'
+
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+  This issue/pr has been automatically marked as stale.
+  It will be closed if no further activity occurs.
+  Thank you for your contributions.
+
+# Comment to post when closing a stale issue. Set to `false` to disable
+closeComment: false

ansible-lint/Dockerfile

@@ -0,0 +1,16 @@
+FROM python:2.7-slim
+
+LABEL "maintainer"="stoe <[email protected]>"
+LABEL "repository"="https://github.com/stoe/actions"
+LABEL "homepage"="https://github.com/stoe/actions"
+LABEL "version"="1.0.0"
+
+LABEL "com.github.actions.name"="ansible-playbook"
+LABEL "com.github.actions.description"="Run Ansible Lint"
+LABEL "com.github.actions.icon"="activity"
+LABEL "com.github.actions.color"="gray-dark"
+
+RUN pip install ansible-lint
+
+ADD entrypoint.sh /entrypoint.sh
+ENTRYPOINT ["/entrypoint.sh"]

ansible-lint/entrypoint.sh

@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+cd "${GITHUB_WORKSPACE}"
+
+ACTION_PLAYBOOK_NAME="${ACTION_PLAYBOOK_NAME:-playbook.yml}"
+ACTION_PLAYBOOK_PATH="${GITHUB_WORKSPACE}/${ACTION_PLAYBOOK_NAME}"
+
+if [ -f "${ACTION_PLAYBOOK_PATH}" ]; then
+  echo
+  echo "==> Linting ${ACTION_PLAYBOOK_PATH}…"
+  ansible-lint "${ACTION_PLAYBOOK_PATH}"
+  echo
+else
+  exit 1
+fi

ansible-lint/license

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) Stefan Stölzle, http://stefan.stoelzle.me
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

ansible-lint/readme.md

@@ -0,0 +1,22 @@
+# Ansible Lint for GitHub Action
+This action allows you to run `ansible-lint` with no additional options.
+
+![](./screenshot.png)
+
+
+## Usage
+To use the action simply add the following lines to your `.github/main.workflow`.
+
+```hcl
+action "Lint Ansible Playbook" {
+  uses = "stoe/actions/ansible-lint@master"
+}
+```
+
+
+### Environment Variables
+- **ACTION_PLAYBOOK_NAME**: (optional) defaults to `playbook.yml`
+
+
+## License
+The Dockerfile and associated scripts and documentation in this project are released under the [MIT](license).

ansible-playbook/Dockerfile

@@ -0,0 +1,16 @@
+FROM python:2.7-slim
+
+LABEL "maintainer"="stoe <[email protected]>"
+LABEL "repository"="https://github.com/stoe/actions"
+LABEL "homepage"="https://github.com/stoe/actions"
+LABEL "version"="1.0.0"
+
+LABEL "com.github.actions.name"="ansible-playbook"
+LABEL "com.github.actions.description"="Run Ansible Playbook"
+LABEL "com.github.actions.icon"="play"
+LABEL "com.github.actions.color"="gray-dark"
+
+RUN pip install ansible
+
+ADD entrypoint.sh /entrypoint.sh
+ENTRYPOINT ["/entrypoint.sh"]

ansible-playbook/entrypoint.sh

@@ -0,0 +1,16 @@
+#!/bin/sh
+set -e
+
+cd "${GITHUB_WORKSPACE}"
+
+ACTION_PLAYBOOK_NAME="${ACTION_PLAYBOOK_NAME:-playbook.yml}"
+ACTION_PLAYBOOK_PATH="${GITHUB_WORKSPACE}/${ACTION_PLAYBOOK_NAME}"
+
+if [ -f "${ACTION_PLAYBOOK_PATH}" ]; then
+  echo
+  echo "==> Running ${ACTION_PLAYBOOK_PATH}…"
+  ansible-playbook "${ACTION_PLAYBOOK_PATH}"
+  echo
+else
+  exit 1
+fi

ansible-playbook/license

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) Stefan Stölzle, http://stefan.stoelzle.me
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

ansible-playbook/readme.md

@@ -0,0 +1,22 @@
+# Ansible Playbook for GitHub Action
+This action allows you to run `ansible-playbook` with no additional options.
+
+![](./screenshot.png)
+
+
+## Usage
+To use the action simply add the following lines to your `.github/main.workflow`.
+
+```hcl
+action "Run Ansible Playbook" {
+  uses = "stoe/actions/ansible-playbook@master"
+}
+```
+
+
+### Environment Variables
+- **ACTION_PLAYBOOK_NAME**: (optional) defaults to `playbook.yml`
+
+
+## License
+The Dockerfile and associated scripts and documentation in this project are released under the [MIT](license).

license

@@ -0,0 +1,21 @@
+The MIT License
+
+Copyright (c) Stefan Stölzle, http://stefan.stoelzle.me
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

readme.md

@@ -0,0 +1,15 @@
+# GitHub Actions
+This is a collection of [GitHub Actions](https://github.com/features/actions) ideas that might be useful.
+
+
+## [Ansible Lint](./ansible-lint/)
+![](./ansible-lint/screenshot.png)
+
+
+## [Ansible Playbook](./ansible-playbook/)
+![](./ansible-playbook/screenshot.png)
+
+
+## License
+[MIT](license).
+Please see additional information in each subdirectory.