Merge pull request #224 from robinmordasiewicz/fork-fortinet-1

feat: new screenshot for azure cloud shell

.github/workflows/screenshots.yml

@@ -6,6 +6,7 @@ on: # yamllint disable-line rule:truthy
     branches:
       - main
     paths:
+      - "docs/img/screenshots/*"
       - ".github/workflows/screenshots.yml"
       - "screenshots.json"
 

doit.sh

@@ -5,6 +5,8 @@
 
 #google-chrome --headless=new --screenshot="docs/img/github-fork-repo.png" --hide-scrollbars --window-size=1620,1080 "https://github.com/robinmordasiewicz/devops-toolkit/fork"
 
+#sgpt "Respond with the markdown syntax that will be used in a README.md file. mkdocs metadata frontmatter with the title, author, date in format %Y-%M-%D, and \"comments: \"true\". Wrap the frontmatter section enclosed in three dashes. In the front matter include comments: true. Do not include a please or thank you. Do not include a welcome message. Do not include a goodbye message. Do not include a signature. Do not include a greeting. Do not include a closing. Do not include a salutation. Do not include a closing salutation. Do not include a closing greeting. Do not include a closing signature. Do not include a closing goodbye message. Do not include a closing welcome message. Create the article in the style of technical instructional blog. Do not include a summary section. Keep the content precise and to the point. Use bullet points and tables to organize the content. Use the markdown syntax for the bullet points and tables. Keep the content concise and to the point. Do not include any fluff. Do not include any filler. Do not include any unnecessary words. Do not include any unnecessary sentences. Do not include any unnecessary paragraphs. Do not include any unnecessary sections. Do not include any unnecessary chapters. Do not include any unnecessary pages. Keep the content length to one page. Make sure that the markdown generated is syntactically correct according to Github README.md style. Make the title of the article three words. Do not include the markdown fence line at the top of the document. The content of the blag article will be about what is the purpose of a folder named .git in a github repository."
+
 #sgpt --code "write a markdown page to let people know how to sign up for github copilot" > docs/github-copilot.md
 #sgpt --code "writes markdown page to describe a demo where a user forks a github repository robinmordasiewicz/devops-toolkit branch named feature1 is created for a user to make their commits. The style guide conventional commits is used as a reference in creating commits. The use will use opencommit command from a zsh shell. In the markdown guide, create steps as an unordered list. Also in the markdown file show the bash commands to execute each step. Give each section a short title. As a pre-requisite instruction, have users install opencommit from github and use the cli command oco to stage, commit and push changes. Highlight a step that demonstrates following style guides for commits such as the conventional commits style guide. The user will use the opencommit command from a zsh shell. In the markdown guide, create steps as an unordered list. Also in the markdown file show the bash commands to execute each step. Give each section a short title." > docs/demo.md
 

tree.sh

@@ -3,5 +3,5 @@
 #File: tree2githubmd
 #Description: Convert output of unix tree utility to Github flavoured Markdown
 
-tree="$(tree -f --noreport --charset ascii $1 | sed -e 's/| \+/  /g' -e 's/[|`]-\+/ */g' -e 's:\(* \)\(\(.*/\)\([^/]\+\)\):\1[\4](\2):g')"
+tree="$(tree -f --noreport --charset ascii "$1" | sed -e 's/| \+/  /g' -e 's/[|`]-\+/ */g' -e 's:\(* \)\(\(.*/\)\([^/]\+\)\):\1[\4](\2):g')"
 printf "# Code/Directory Structure:\n%s\n" "${tree}"