Release documents

Author: phazonoverload

.github/CODEOWNERS

@@ -0,0 +1,2 @@
+# This repository is maintained by: 
+* @phazonoverload @ashleywolf

.github/workflows/dependabot.yml

@@ -0,0 +1,6 @@
+version: 2
+updates:
+  - package-ecosystem: 'github-actions'
+    directory: '/'
+    schedule:
+      interval: 'weekly'

CONTRIBUTING.md

@@ -0,0 +1,32 @@
+## Contributing
+
+[fork]: https://github.com/github-samples/models-in-actions/fork
+[pr]: https://github.com/github-samples/models-in-actions/compare
+
+Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
+
+Contributions to this project are [released](https://help.github.com/articles/github-terms-of-service/#6-contributions-under-repository-license) to the public under the [project's open source license](LICENSE).
+
+Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
+
+## Submitting a pull request
+
+1. [Fork][fork] and clone the repository
+1. Add your workflows to the `workflows` directory. Each action should be in its own subdirectory, and the name of the subdirectory should match the name of the action.
+1. Make sure your workflow file has setup instruction at the top of it in comments.
+1. Make sure to add a `README.md` file in the action's subdirectory. This file should describe what the action does, how to use it, and any inputs or outputs it has.
+1. Make sure to add your action to the `README.md` file in the root of the repository. This file should list all the actions in the repository and provide a brief description of each one.
+1. Push to your fork and [submit a pull request][pr]
+1. Pat yourself 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:
+
+- Show what the output of the workflow looks like. If you can, include a screenshot or a link to a run of the workflow in your pull request description.
+- Only submit one workflow per pull request. This makes it easier for us to review and merge your changes.
+- Write a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+
+## 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)

README.md

@@ -1,14 +1,20 @@
-# Walkthrough Template
+# GitHub Models in GitHub Actions
 
-This repository serves as a template for creating a walkthrough. Follow the steps below to get started.
+This repository contains a collection of [GitHub Actions](https://github.com/features/actions) workflows that utilize [GitHub Models](https://docs.github.com/en/github-models) to automate various tasks with AI.
 
-## Getting Started
+| Title | Description | Author |
+| [Weekly Issue Summary](/workflows/weekly-issue-summary/weekly-issue-summary.yml) | Opens a new issue weekly summarizing the issues created in the last week. | @phazonoverload |
+| [Bug Reproduction Check](/workflows/bug-reproduction-check/bug-reproduction-check.yml) | Comments with request for better reproduction details, if needed. | @phazonoverload |
+| [Add Merged PR to Changelog](/workflows/add-merged-pr-to-changelog/add-merged-pr-to-changelog.yml) | Appends a summary of a merged pull request to an issue. | @phazonoverload |
 
-1. Clone this repository.
-2. Update the documentation in the `docs` folder (including the `README.md` folder).
-3. Customize the code and other content as needed.
-4. Update the `SUPPORT.md` file with the appropriate information.
-5. Review the default LICENSE (MIT), CODE_OF_CONDUCT, and CONTRIBUTING files to ensure they meet your needs. These use the samples provided as part of the OSPO release process.
-6. Update the `README.md` file in the repository root with the appropriate information. You can find an example at [github-samples/game-of-life-walkthrough](https://github.com/github-samples/game-of-life-walkthrough).
-7. Update the [devcontainer template](.devcontainer/devcontainer.json) so that it has all the needed tools, frameworks and extensions installed so those using your sample can get going quickly.
-8. When you are ready to publish the repository, please make sure that the Git history is clean. Then, raise an issue for a 'sample release' at [https://github.com/github/open-source-releases](https://github.com/github/open-source-releases).
+## License 
+
+This project is licensed under the terms of the MIT open source license. Please refer to [MIT](./LICENSE) for the full terms.
+
+## Maintainers 
+
+See maintainers in the [CODEOWNERS](https://github.com/github-samples/models-in-actions/blob/main/.github/CODEOWNERS) file.
+
+## Support
+
+Our team will try their best to respond to issues and pull requests in a timely manner. However, please note that this is an open source project and support may be limited.

SUPPORT.md

@@ -1,20 +1,12 @@
-
-# TODO: The maintainer of this repo has not updated this file
-
 # Support 
 
 ## How to file issues and get help
 
 This project uses GitHub issues to track bugs and feature requests. Please search the existing issues before filing new issues to avoid duplicates. For new issues, file your bug or feature request as a new issue.
 
-For help or questions about using this project, please **TODO:** REPO MAINTAINER TO INSERT INSTRUCTIONS ON HOW TO ENGAGE REPO OWNERS OR COMMUNITY FOR HELP. COULD BE A SLACK OR DISCORD OR OTHER CHANNEL FOR HELP. WHERE WILL YOU HELP PEOPLE?
-
-**TODO: REPO MAINTAINERS** Please include one of the following statements file:
+For help or questions about using this project, please open issues on this repository. 
 
-- **THIS PROJECT NAME** is under active development and maintained by GitHub staff **AND THE COMMUNITY**. We will do our best to respond to support, feature requests, and community questions in a timely manner.
-- **THIS PROJECT NAME** is not actively developed but is maintained by GitHub staff **AND THE COMMUNITY**. We will do our best to respond to support and community questions in a timely manner. 
-- **THIS PROJECT NAME** is no longer supported or maintained by GitHub staff. We will not respond to support or community questions.
-- **THIS PROJECT NAME** is archived and deprecated. As an unsupported project, feel free to fork.
+This collection of workflows is under active development and maintained by GitHub staff **AND THE COMMUNITY**. We will do our best to respond to support, feature requests, and community questions in a timely manner.
 
 ## GitHub Support Policy