update to use official docs

Author: SomayaB

CONTRIBUTING.md

@@ -1,81 +1,61 @@
 # Contributing Guidelines
 
-Thank you for your interest in contributing to our project. Whether it's
-a bug report, new feature, correction, or additional documentation, we
-greatly value feedback and contributions from our community.
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
+information to effectively respond to your bug report or contribution.
 
-Please read through this document before submitting any issues or pull
-requests to ensure we have all the necessary information to effectively
-respond to your bug report or contribution.
 
 ## Reporting Bugs/Feature Requests
 
-We welcome you to use the GitHub issue tracker to report bugs or suggest
-features.
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
 
-When filing an issue, please check
-[existing open](https://github.com/aws-actions/stale-issue-cleanup/issues),
-or [recently closed](https://github.com/aws-actions/stale-issue-cleanup/issues?utf8=%E2%9C%93&=is%3Aissue%20is%3Aclosed%20),
-issues to make sure somebody else hasn't already reported the issue.
-Please try to include as much information as you can. Details like these
-are incredibly useful:
+When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
 
 * A reproducible test case or series of steps
 * The version of our code being used
 * Any modifications you've made relevant to the bug
 * Anything unusual about your environment or deployment
 
+
 ## Contributing via Pull Requests
-Contributions via pull requests are much appreciated. Before sending us a
-pull request, please ensure that:
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
 
 1. You are working against the latest source on the *master* branch.
-2. You check existing open, and recently merged, pull requests to make
-   sure someone else hasn't addressed the problem already.
-3. You open an issue to discuss any significant work - we would hate for
-   your time to be wasted.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
 
 To send us a pull request, please:
 
 1. Fork the repository.
-2. Modify the source; please focus on the specific change you are
-   contributing. If you also reformat all the code, it will be hard for
-   us to focus on your change.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
 3. Ensure local tests pass.
 4. Commit to your fork using clear commit messages.
-5. Send us a pull request, answering any default questions in the pull
-   request interface.
-6. Pay attention to any automated CI failures reported in the pull
-   request, and stay involved in the conversation.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
 
-GitHub provides additional documentation on [forking a repository](https://help.github.com/articles/fork-a-repo/)
-and [creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
 
 
 ## Finding contributions to work on
-Looking at the existing issues is a great way to find something to
-contribute on. As our projects, by default, use the default GitHub issue
-labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix),
-looking at any ['help wanted'](https://github.com/aws-actions/stale-issue-cleanup/labels/help%20wanted)
-issues is a great place to start.
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
+
 
 ## Code of Conduct
 This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+[email protected] with any additional questions or comments.
 
-For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq)
-or contact [email protected] with any additional
-questions or comments.
 
 ## Security issue notifications
-If you discover a potential security issue in this project we ask that
-you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/).
-Please do **not** create a public github issue.
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+
 
 ## Licensing
 
-See the [LICENSE](https://github.com/aws-actions/stale-issue-cleanup/blob/master/LICENSE)
-file for our project's licensing. We will ask you to confirm the
-licensing of your contribution.
+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
 
-We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement)
-for larger changes.
+We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.

NOTICE

@@ -1 +1 @@
-Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
+Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.

README.md

@@ -1,27 +1,46 @@
-# Closed Issues Message
+## Closed Issue Message
 
 This action sets a default message to be commented on all issues when they get closed.
 
-## Inputs
+## Usage
 
-### `closed-issues-message`
+Add a YAML workflow file into your repository under
+`.github/workflows`. 
+This workflow file follows the 
+[standard workflow syntax for Github Actions](https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions).
 
-**Required** The message you want to be commented whenever an issue is closed.
-
-## Example workflow
+For a list of options and their description, see [action.yml](./action.yml).
 
+### Example Workflow
 ```yml
-name: Closed Issues Message
+name: Closed Issue Message
 on:
     issues:
        types: [closed]
 jobs:
     auto_comment:
         runs-on: ubuntu-latest
         steps:
-        - uses: SomayaB/closed-issues-message
+        - uses: aws-actions/closed-issue-message
             with:
             # These inputs are both required
             repo-token: "${{ secrets.GITHUB_TOKEN }}"
-            closed-issues-message: "Warning: comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or        open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so." 
+            message: "Comments on closed issues are hard for our team to see." 
+```
+> You can do a multi line comment by using a pipe: 
+```yml
+message: |
+         ### ⚠️COMMENT VISIBILITY WARNING⚠️ 
+         Comments on closed issues are hard for our team to see. 
+         If you need more assistance, please either tag a team member or open a new issue that references this one. 
+         If you wish to keep having a conversation with other community members under this issue feel free to do so.
+                                    
 ```
+![closed issue message example](comment-example.png)
+## Security
+
+See [CONTRIBUTING](CONTRIBUTING.md#security-issue-notifications) for more information.
+
+## License
+
+This project is licensed under the Apache-2.0 License.