[DOCS] Open source updates

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,6 @@
+---
+blank_issues_enabled: false
+contact_links:
+  - name: General Questions
+    url: https://github.com/github/actions-migrations-via-copilot/discussions
+    about: Ask questions and discuss ideas in GitHub Discussions

.github/ISSUE_TEMPLATE/documentation.md

@@ -0,0 +1,26 @@
+---
+name: Documentation Improvement
+about: Suggest improvements to deployment, operations, or other documentation
+title: '[DOCS]'
+labels: 'documentation'
+assignees: ''
+---
+
+**Which documentation area does this relate to?**
+- [ ] Deployment Guide (`docs/deployment.md`)
+- [ ] Operations Guide (`docs/operations.md`)
+- [ ] README
+- [ ] Contributing Guide
+- [ ] New documentation needed
+
+**Describe the improvement**
+A clear and concise description of what should be added, changed, or clarified.
+
+**Current documentation issue (if applicable)**
+Describe what is missing, unclear, or incorrect in the current documentation.
+
+**Proposed content or changes**
+Outline the content or changes you'd like to see.
+
+**Additional context**
+Add any other context, links to related issues, or examples from other projects.

.github/ISSUE_TEMPLATE/knowledgebase.md

@@ -0,0 +1,42 @@
+---
+name: Knowledgebase Update
+about: Suggest updates to action mappings, patterns, or best practices
+title: '[KNOWLEDGE]'
+labels: 'knowledgebase'
+assignees: ''
+---
+
+**Which knowledgebase area does this relate to?**
+- [ ] Action Mappings (`knowledge/actions-mapping/`)
+- [ ] Security Patterns (`knowledge/patterns/`)
+- [ ] Report Templates (`knowledge/report-template/`)
+- [ ] Migration Standards (`knowledge/migration-standards.md`)
+- [ ] Migration Guardrails (`knowledge/migration-guardrails.md`)
+- [ ] Migration Workflow (`knowledge/migration-workflow.md`)
+
+**Which CI/CD platform does this relate to? (if applicable)**
+- [ ] Jenkins
+- [ ] Azure DevOps
+- [ ] CircleCI
+- [ ] GitLab
+- [ ] Travis CI
+- [ ] Bamboo
+- [ ] Bitbucket
+- [ ] Drone CI
+- [ ] General / All platforms
+
+**Describe the update**
+A clear and concise description of what should be added or changed.
+
+**Source plugin/task/command**
+```
+# The CI/CD plugin, task, or command that needs mapping
+```
+
+**Proposed GitHub Actions equivalent**
+```yaml
+# The GitHub Actions equivalent or pattern
+```
+
+**Additional context**
+Add any documentation links, examples, or other context that supports this update.

.github/ISSUE_TEMPLATE/migration_agent.md

@@ -0,0 +1,44 @@
+---
+name: Migration Agent Improvement
+about: Suggest improvements or report issues with migration agents
+title: '[AGENT]'
+labels: 'agents'
+assignees: ''
+---
+
+**Which migration agent does this relate to?**
+- [ ] Jenkins Migrator
+- [ ] Azure DevOps Migrator
+- [ ] CircleCI Migrator
+- [ ] GitLab Migrator
+- [ ] Travis CI Migrator
+- [ ] Bamboo Migrator
+- [ ] Bitbucket Migrator
+- [ ] Drone CI Migrator
+- [ ] Reusable Workflow Builder
+- [ ] New platform (please specify)
+
+**Is this a bug or an improvement?**
+- [ ] Bug - Agent produces incorrect output
+- [ ] Improvement - Agent could handle this better
+
+**Describe the issue or improvement**
+A clear and concise description of the problem or enhancement.
+
+**Source CI/CD configuration (if applicable)**
+```yaml
+# Paste the source CI/CD configuration that the agent struggles with
+```
+
+**Expected GitHub Actions output**
+```yaml
+# Paste the expected GitHub Actions workflow output
+```
+
+**Actual output (if bug)**
+```yaml
+# Paste the actual output the agent produced
+```
+
+**Additional context**
+Add any other context, screenshots, or migration report excerpts here.

.github/ISSUE_TEMPLATE/migration_automation.md

@@ -0,0 +1,39 @@
+---
+name: Migration Automation Improvement
+about: Suggest improvements to bulk migration workflows and automation
+title: '[AUTOMATION]'
+labels: 'automation'
+assignees: ''
+---
+
+**What type of automation improvement is this?**
+- [ ] New automation capability
+- [ ] Enhancement to existing workflow
+- [ ] Bug fix for automation
+- [ ] Performance optimization
+- [ ] Scheduling/trigger improvement
+
+**Describe the improvement or issue**
+A clear and concise description of the automation enhancement or problem.
+
+**Use case**
+Describe the scenario where this automation improvement would be beneficial.
+
+**Current behavior (if applicable)**
+Describe how the automation currently works.
+
+**Expected behavior**
+Describe how the automation should work after this improvement.
+
+**Proposed implementation (optional)**
+```yaml
+# Outline the workflow changes or new automation approach
+```
+
+**Scale considerations**
+- Approximate number of repositories this would affect:
+- Expected frequency of execution:
+- Any rate limiting or resource concerns:
+
+**Additional context**
+Add any other context, error logs, or workflow run links here.

.github/dependabot.yml

@@ -0,0 +1,20 @@
+# Dependabot configuration for automated dependency updates
+# See: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
+
+version: 2
+updates:
+  # Maintain dependencies for GitHub Actions
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+      day: "monday"
+    open-pull-requests-limit: 5
+    groups:
+      # Group GitHub official actions
+      github-actions:
+        patterns:
+          - "actions/*"
+    labels:
+      - "dependencies"
+      - "github-actions"

.github/release.yml

@@ -0,0 +1,28 @@
+# Configuration for GitHub's auto-generated release notes
+# https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
+
+changelog:
+  exclude:
+    labels:
+      - ignore-for-release
+      - duplicate
+      - invalid
+      - wontfix
+    authors:
+      - dependabot
+  categories:
+    - title: 🤖 Migration Agent Improvements
+      labels:
+        - agents
+    - title: 📚 Knowledgebase Updates
+      labels:
+        - knowledgebase
+    - title: 🔄 Migration Automation
+      labels:
+        - automation
+    - title: 📖 Documentation
+      labels:
+        - documentation
+    - title: Other Changes
+      labels:
+        - "*"

CODE_OF_CONDUCT.md

@@ -0,0 +1,74 @@
+# 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 <opensource@github.com>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and 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/

CONTRIBUTING.md

@@ -0,0 +1,95 @@
+# Contributing
+
+:wave: Hi there!
+We're thrilled that you'd like to contribute to the GitHub Actions Migration Agents project. Your help is essential for keeping our migration agents, knowledgebase, and patterns up-to-date and effective.
+
+## Ways to Contribute
+
+### Migration Agents (`agents/`)
+
+- Improve existing migration agent prompts for better accuracy
+- Add support for new CI/CD platforms
+- Enhance agent instructions based on real-world migration feedback
+
+### Knowledgebase (`knowledge/`)
+
+- Add or update action mappings for CI/CD plugins and tasks
+- Document new migration patterns and best practices
+- Improve security patterns for credential handling
+- Expand report templates with additional insights
+
+### Documentation (`docs/`)
+
+- Improve deployment and operations guides
+- Add troubleshooting tips and FAQs
+- Document edge cases and workarounds
+
+### Migration Automation (`.github/workflows/`)
+
+- Enhance bulk migration workflows
+- Improve automation triggers and scheduling
+- Add new automation capabilities for enterprise-scale migrations
+- Optimize workflow performance and reliability
+
+## Submitting a Pull Request
+
+[Pull Requests][pulls] are used for adding new agents, patterns, mappings, and documentation, or improving existing ones.
+
+### With Write Access
+
+1. Clone the repository
+1. Create a new branch: `git checkout -b my-branch-name`
+1. Make your changes
+1. Push and [submit a pull request][pr]
+1. Wait for your pull request to be reviewed and merged
+
+### Without Write Access
+
+1. [Fork][fork] and clone the repository
+1. Create a new branch: `git checkout -b my-branch-name`
+1. Make your changes
+1. Push to your fork and [submit a pull request][pr]
+1. Wait for your pull request to be reviewed and merged
+
+### Tips for a Successful PR
+
+- 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 [good commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
+- Test agent changes with real CI/CD configurations when possible.
+- Follow the existing structure and formatting conventions in the knowledgebase.
+
+Work in Progress pull requests are also welcome to get feedback early on, or if there is something blocking you.
+
+- Create a branch with a name that identifies the user and nature of the changes (similar to `user/branch-purpose`)
+- Open a pull request and mark it as a draft
+
+## Adding a New CI/CD Platform
+
+To add support for a new CI/CD platform:
+
+1. Create a new agent file in `agents/` (follow existing agent structure)
+2. Add action mappings in `knowledge/actions-mapping/`
+3. Add security patterns in `knowledge/patterns/<platform>/`
+4. Add a report template in `knowledge/report-template/`
+5. Update the README.md to include the new platform
+
+## Releasing
+
+If you are a maintainer of this project:
+
+1. Create a [Tag](https://stackoverflow.com/questions/18216991/create-a-tag-in-a-github-repository) following semantic versioning
+2. Draft a [Release](https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository) document explaining the changes
+3. Obtain approval from [CODEOWNERS](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners)
+
+## 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 Actions Documentation](https://docs.github.com/en/actions)
+- [GitHub Copilot Custom Agents](https://docs.github.com/en/copilot)
+- [Workflow Syntax for GitHub Actions](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions)
+
+[pulls]: https://github.com/github/actions-migrations-via-copilot/pulls
+[pr]: https://github.com/github/actions-migrations-via-copilot/compare
+[fork]: https://github.com/github/actions-migrations-via-copilot/fork