Merge pull request #22 from Latrodect/development

Development to master

Author: Latrodect

CHANGELOG.md

@@ -1,9 +1,13 @@
-# Change Log
+# Changelog
 
-All notable changes to the "backdoor" extension will be documented in this file.
+## [Unreleased]
+- New feature or enhancement
 
-Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how to structure this file.
+## [1.1.2] - 2023-08-10
+- Initial release
 
-## [Unreleased]
+When creating docker-compose.yaml, user can insert multiple environment variables.(New Feature)
+Also some bugs are fixed.
+K8S file and Dockerfile generation command indent error fixed.
 
-- Initial release
+[1.1.2]: https://github.com/Latrodect/Backdoor-VSCode-Extension-for-K8S-Setup-and-Code-Review/releases/tag/v1.1.2

CONTRIBUTING.md

@@ -0,0 +1,50 @@
+# Contributing to Backdoor
+
+Thank you for your interest in contributing to Backdoor! We welcome contributions from the community to help improve and enhance the extension. By contributing, you are helping to make this extension better for everyone.
+
+## Table of Contents
+
+- [Getting Started](#getting-started)
+- [Issues](#issues)
+- [Pull Requests](#pull-requests)
+- [Code of Conduct](#code-of-conduct)
+
+## Getting Started
+
+Before you start contributing, please make sure you have the following prerequisites:
+
+- [Node.js](https://nodejs.org/) and npm installed.
+- [Visual Studio Code](https://code.visualstudio.com/) editor.
+
+Follow these steps to contribute:
+
+1. Fork the repository on GitHub.
+2. Clone your forked repository locally.
+3. Install dependencies by running: `npm install`
+4. Make your changes and improvements.
+5. Test your changes with: `npm test`
+6. Commit your changes and create a descriptive commit message.
+7. Push your changes to your fork on GitHub.
+8. Create a pull request (PR) to the main repository.
+
+## Issues
+
+If you find a bug, have a question, or want to suggest a feature, please open an issue on the [issue tracker](https://github.com/your-username/your-extension/issues). Before opening an issue, please search existing issues to see if it has already been reported or discussed.
+
+## Pull Requests
+
+We welcome pull requests from contributors. When creating a pull request, please:
+
+1. Fork the repository and create a new branch for your feature or bug fix.
+2. Follow the [Angular Commit Message Conventions](https://github.com/angular/angular.js/blob/master/DEVELOPERS.md#-git-commit-guidelines) for your commit messages.
+3. Write a clear and concise description of your pull request and the changes you've made.
+4. Make sure your code passes all tests and linting rules.
+5. Include relevant tests for your changes if applicable.
+
+## Code of Conduct
+
+Please note that this project has a [Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project, you agree to abide by its terms.
+
+Thank you for contributing to [Your Extension Name]! Your contributions are greatly appreciated.
+
+Happy coding!