Merge branch 'MichaelCade:main' into main

Author: qmauvnt

.github/workflows/Auto_message_on_creatingissues.yml

@@ -0,0 +1,16 @@
+name: Auto message on Creating a Issue.
+
+on:
+  issues:
+    types: [opened]
+
+jobs:
+  greeting:
+    runs-on: ubuntu-latest
+    steps:
+    - name: Create comment for issue
+      if: github.event_name =='issues'
+      uses: peter-evans/create-or-update-comment@v1
+      with:
+        issue-number: ${{tojson(github.event.issue.number)}}
+        body: Hello there!👋, @${{ github.actor }} Welcome to the Solidity-Pathshala! 🚀⚡Thank you and Congratulations🎉 for opening a issue in this project. Please make sure not to start working on this issue, unless you are assigned to it.😄

.github/workflows/Auto_message_on_pr_merge.yml

@@ -0,0 +1,19 @@
+name: Auto message on Pr merge
+
+on:
+  pull_request_target:
+    types: [closed]
+
+jobs:
+  auto-response:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: derekprior/add-autoresponse@master
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        respondableId: ${{ github.event.pull_request.node_id }}
+        response: "Thank you @${{ github.event.pull_request.user.login }} for taking out your valuable time in order to contribute to our project. Looking forward for more such amazing contributions :)"
+        author: ${{ github.event.pull_request.user.login }}
+        exemptedAuthors: "Vikash-8090-Yadav"

.github/workflows/Auto_message_on_pr_open.yml

@@ -0,0 +1,19 @@
+name: Auto message on PR opened
+
+on:
+  pull_request_target:
+    types: [opened]
+
+jobs:
+  auto-response:
+    runs-on: ubuntu-latest
+
+    steps:
+    - uses: derekprior/add-autoresponse@master
+      env:
+        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      with:
+        respondableId: ${{ github.event.pull_request.node_id }}
+        response: "Our team will soon review your PR. Thanks @${{ github.event.pull_request.user.login }} :)"
+        author: ${{ github.event.pull_request.user.login }}
+        exemptedAuthors: "Vikash-8090-Yadav"

2022/Days/day37.md

@@ -71,10 +71,10 @@ I have taken these from [atlassian](https://www.atlassian.com/git/tutorials/atla
 | Command       | Example                     | Description                                                                                                                 |
 | ------------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
 | git init      | `git init <directory>`      | Create an empty git repository in the specified directory.                                                                  |
-| git clone     | `git clone <repo>`          | Clone repository located at <repo> onto local machine.                                                                      |
+| git clone     | `git clone <repo>`          | Clone repository located at \<repo> onto local machine.                                                                      |
 | git config    | `git config user.name`      | Define author name to be used for all commits in current repository `system`, `global`, `local` flag to set config options. |
-| git add       | `git add <directory>`       | Stage all changes in <directory> for the next commit. We can also add <files> and <.> for everything.                       |
-| git commit -m | `git commit -m "<message>"` | Commit the staged snapshot, use <message> to detail what is being committed.                                                |
+| git add       | `git add <directory>`       | Stage all changes in \<directory> for the next commit. We can also add \<files> and \<.> for everything.                       |
+| git commit -m | `git commit -m "<message>"` | Commit the staged snapshot, use \<message> to detail what is being committed.                                                |
 | git status    | `git status`                | List files that are staged, unstaged and untracked.                                                                         |
 | git log       | `git log`                   | Display all commit history using the default format. There are additional options with this command.                        |
 | git diff      | `git diff`                  | Show unstaged changes between your index and working directory.                                                             |
@@ -83,34 +83,34 @@ I have taken these from [atlassian](https://www.atlassian.com/git/tutorials/atla
 
 | Command    | Example               | Description                                                                                                                           |
 | ---------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------- |
-| git revert | `git revert <commit>` | Create a new commit that undoes all of the changes made in <commit> then apply it to the current branch.                              |
-| git reset  | `git reset <file>`    | Remove <file> from the staging area, but leave the working directory unchanged. This unstaged a file without overwriting any changes. |
+| git revert | `git revert <commit>` | Create a new commit that undoes all of the changes made in \<commit> then apply it to the current branch.                              |
+| git reset  | `git reset <file>`    | Remove \<file> from the staging area, but leave the working directory unchanged. This unstaged a file without overwriting any changes. |
 | git clean  | `git clean -n`        | Shows which files would be removed from the working directory. Use `-f` in place of `-n` to execute the clean.                        |
 
 ### Git Rewriting History
 
 | Command    | Example              | Description                                                                                                                              |
 | ---------- | -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
 | git commit | `git commit --amend` | Replace the last commit with the staged changes and the last commit combined. Use with nothing staged to edit the last commit’s message. |
-| git rebase | `git rebase <base>`  | Rebase the current branch onto <base>. <base> can be a commit ID, branch name, a tag, or a relative reference to HEAD.                   |
+| git rebase | `git rebase <base>`  | Rebase the current branch onto \<base>. \<base> can be a commit ID, branch name, a tag, or a relative reference to HEAD.                   |
 | git reflog | `git reflog`         | Show a log of changes to the local repository’s HEAD. Add --relative-date flag to show date info or --all to show all refs.              |
 
 ### Git Branches
 
 | Command      | Example                    | Description                                                                                                   |
 | ------------ | -------------------------- | ------------------------------------------------------------------------------------------------------------- |
-| git branch   | `git branch`               | List all of the branches in your repo. Add a <branch> argument to create a new branch with the name <branch>. |
-| git checkout | `git checkout -b <branch>` | Create and check out a new branch named <branch>. Drop the -b flag to checkout an existing branch.            |
-| git merge    | `git merge <branch>`       | Merge <branch> into the current branch.                                                                       |
+| git branch   | `git branch`               | List all of the branches in your repo. Add a \<branch> argument to create a new branch with the name \<branch>. |
+| git checkout | `git checkout -b <branch>` | Create and check out a new branch named \<branch>. Drop the -b flag to checkout an existing branch.            |
+| git merge    | `git merge <branch>`       | Merge \<branch> into the current branch.                                                                       |
 
 ### Git Remote Repositories
 
 | Command        | Example                       | Description                                                                                                                         |
 | -------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
-| git remote add | `git remote add <name> <url>` | Create a new connection to a remote repo. After adding a remote, you can use <name> as a shortcut for <url> in other commands.      |
-| git fetch      | `git fetch <remote> <branch>` | Fetches a specific <branch>, from the repo. Leave off <branch> to fetch all remote refs.                                            |
+| git remote add | `git remote add <name> <url>` | Create a new connection to a remote repo. After adding a remote, you can use \<name> as a shortcut for \<url> in other commands.      |
+| git fetch      | `git fetch <remote> <branch>` | Fetches a specific \<branch>, from the repo. Leave off \<branch> to fetch all remote refs.                                            |
 | git pull       | `git pull <remote>`           | Fetch the specified remote’s copy of current branch and immediately merge it into the local copy.                                   |
-| git push       | `git push <remote> <branch>`  | Push the branch to <remote>, along with necessary commits and objects. Creates named branch in the remote repo if it doesn’t exist. |
+| git push       | `git push <remote> <branch>`  | Push the branch to \<remote>, along with necessary commits and objects. Creates named branch in the remote repo if it doesn’t exist. |
 
 ### Git Diff
 
@@ -123,40 +123,40 @@ I have taken these from [atlassian](https://www.atlassian.com/git/tutorials/atla
 
 | Command                                              | Example                                                | Description                                                                                                                                   |
 | ---------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| git config --global user.name <name>                 | `git config --global user.name <name>`                 | Define the author name to be used for all commits by the current user.                                                                        |
-| git config --global user.email <email>               | `git config --global user.email <email>`               | Define author email to be used for all commits by the current user.                                                                           |
-| git config --global alias <alias-name> <git-command> | `git config --global alias <alias-name> <git-command>` | Create shortcut for a git command .                                                                                                           |
-| git config --system core.editor <editor>             | `git config --system core.editor <editor>`             | Set the text editor to be used by commands for all users on the machine. <editor> arg should be the comamnd that launches the desired editor. |
+| git config --global user.name \<name>                 | `git config --global user.name <name>`                 | Define the author name to be used for all commits by the current user.                                                                        |
+| git config --global user.email \<email>               | `git config --global user.email <email>`               | Define author email to be used for all commits by the current user.                                                                           |
+| git config --global alias \<alias-name> \<git-command> | `git config --global alias <alias-name> <git-command>` | Create shortcut for a git command .                                                                                                           |
+| git config --system core.editor \<editor>             | `git config --system core.editor <editor>`             | Set the text editor to be used by commands for all users on the machine. \<editor> arg should be the comamnd that launches the desired editor. |
 | git config --global --edit                           | `git config --global --edit `                          | Open the global configuration file in a text editor for manual editing.                                                                       |
 
 ### Git Rebase
 
 | Command              | Example                | Description                                                                                                                                 |
 | -------------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
-| git rebase -i <base> | `git rebase -i <base>` | Interactively rebase current branch onto <base>. Launches editor to enter commands for how each commit will be transferred to the new base. |
+| git rebase -i \<base> | `git rebase -i <base>` | Interactively rebase current branch onto \<base>. Launches editor to enter commands for how each commit will be transferred to the new base. |
 
 ### Git Pull
 
 | Command                    | Example                      | Description                                                                                                                                   |
 | -------------------------- | ---------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
-| git pull --rebase <remote> | `git pull --rebase <remote>` | Fetch the remote’s copy of current branch and rebases it into the local copy. Uses git rebase instead of the merge to integrate the branches. |
+| git pull --rebase \<remote> | `git pull --rebase <remote>` | Fetch the remote’s copy of current branch and rebases it into the local copy. Uses git rebase instead of the merge to integrate the branches. |
 
 ### Git Reset
 
 | Command                   | Example                     | Description                                                                                                                                   |
 | ------------------------- | --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
 | git reset                 | `git reset `                | Reset the staging area to match the most recent commit but leave the working directory unchanged.                                             |
 | git reset --hard          | `git reset --hard`          | Reset staging area and working directory to match most recent commit and overwrites all changes in the working directory                      |
-| git reset <commit>        | `git reset <commit>`        | Move the current branch tip backwards to <commit>, reset the staging area to match, but leave the working directory alone                     |
-| git reset --hard <commit> | `git reset --hard <commit>` | Same as previous, but resets both the staging area & working directory to match. Deletes uncommitted changes, and all commits after <commit>. |
+| git reset \<commit>        | `git reset <commit>`        | Move the current branch tip backwards to \<commit>, reset the staging area to match, but leave the working directory alone                     |
+| git reset --hard \<commit> | `git reset --hard <commit>` | Same as previous, but resets both the staging area & working directory to match. Deletes uncommitted changes, and all commits after \<commit>. |
 
 ### Git Push
 
 | Command                   | Example                     | Description                                                                                                                                     |
 | ------------------------- | --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| git push <remote> --force | `git push <remote> --force` | Forces the git push even if it results in a non-fast-forward merge. Do not use the --force flag unless you’re sure you know what you’re doing.  |
-| git push <remote> --all   | `git push <remote> --all`   | Push all of your local branches to the specified remote.                                                                                        |
-| git push <remote> --tags  | `git push <remote> --tags`  | Tags aren’t automatically pushed when you push a branch or use the --all flag. The --tags flag sends all of your local tags to the remote repo. |
+| git push \<remote> --force | `git push <remote> --force` | Forces the git push even if it results in a non-fast-forward merge. Do not use the --force flag unless you’re sure you know what you’re doing.  |
+| git push \<remote> --all   | `git push <remote> --all`   | Push all of your local branches to the specified remote.                                                                                        |
+| git push \<remote> --tags  | `git push <remote> --tags`  | Tags aren’t automatically pushed when you push a branch or use the --all flag. The --tags flag sends all of your local tags to the remote repo. |
 
 ## Resources
 

2022/Days/day63.md

@@ -95,7 +95,7 @@ I think it is important to touch on some of the differences between Ansible and
 | Language       | Ansible follows procedural language                          | Terraform follows a declarative language                          |
 | Provisioning   | Ansible provides partial provisioning (VM, Network, Storage) | Terraform provides extensive provisioning (VM, Network, Storage) |
 | Packaging      | Ansible provides complete support for packaging & templating | Terraform provides partial support for packaging & templating    |
-| Lifecycle Mgmt | Ansible does not have lifecycle management                   | Terraform is heavily dependent on lifecycle and state mgmt       |
+| Lifecycle Mgmt | Ansible does not have lifecycle management                   | Terraform is heavily dependent on lifecycle and state management  |
 
 ## Resources
 

2022/Days/day64.md

@@ -37,7 +37,7 @@ Before we then start to look at controlling other nodes in our environment, we c
 
 ![](Images/Day64_config2.png)
 
-Or an actual real-life use for a module might be something like `ansible webservers --m service -a "name=httpd state=started"` this will tell us if all of our webservers have the httpd service running. I have glossed over the webservers term used in that command.
+Or an actual real-life use for a module might be something like `ansible webservers -m service -a "name=httpd state=started"` this will tell us if all of our webservers have the httpd service running. I have glossed over the webservers term used in that command.
 
 ### hosts
 

2022/Days/day84.md

@@ -12,7 +12,7 @@ id: 1048747
 
 ![](Images/Day84_Data1.png)
 
-Data Management is by no means a new wall to climb, although we do know that data is more important than it maybe was a few years ago. Valuable and ever-changing it can also be a massive nightmare when we are talking about automation and continuously integrating, testing and deploying frequent software releases. Enter the persistent data and underlying data services are often the main culprit when things go wrong.
+Data Management is by no means a new wall to climb, although we do know that data is more important than it may be was a few years ago. Valuable and ever-changing it can also be a massive nightmare when we are talking about automation and continuously integrating, testing and deploying frequent software releases. Enter the persistent data and underlying data services are often the main culprit when things go wrong.
 
 But before I get into Cloud-Native Data Management, we need to go up a level. We have touched on many different platforms throughout this challenge. Be it Physical, Virtual, Cloud or Cloud-Native obviously including Kubernetes there is none of these platforms that provide the lack of requirement for data management.